[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable bisection] complete test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm



On 30/10/16 04:29, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
> testid debian-hvm-install
>
> Tree: linux git://xenbits.xen.org/linux-pvops.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: xen git://xenbits.xen.org/xen.git
>
> *** Found and reproduced problem changeset ***
>
>   Bug is in tree:  xen git://xenbits.xen.org/xen.git
>   Bug introduced:  0897514b4b376a167f968f79c6ea0dee1061458e
>   Bug not present: 4000a7c7d7b0e01837abd3918e393f289c07d68c
>   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/101803/
>
>
>   commit 0897514b4b376a167f968f79c6ea0dee1061458e
>   Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
>   Date:   Wed Oct 26 10:34:21 2016 +0100
>   
>       tools/oxenstored: Avoid allocating invalid transaction ids

Looking at xenstored-access.log before:

A8.1         write     /vm/6fc3ae48-3d32-4710-aaac-55801d273773/uuid
6fc3ae48-3d32-4710-aaac-55801d273773
A8.1         write     /vm/6fc3ae48-3d32-4710-aaac-55801d273773/name
debianhvm.guest.osstest
A8.1         write    
/local/domain/1/control/platform-feature-multiprocessor-suspend 1
A8.1         write    
/local/domain/1/control/platform-feature-xs_reset_watches 1
A8.1         commit
A8           write     /libxl/1/dm-version qemu_xen_traditional
A8.2         write     /local/domain/1/memory/static-max 5120000
A8.2         write     /local/domain/1/memory/target 5115904
A8.2         write     /local/domain/1/memory/videoram 4096
A8.2         write     /local/domain/1/domid 1

And after:

A8.1         write     /vm/0a3c1b35-33f8-432d-aab7-b98ea16d490f/uuid
0a3c1b35-33f8-432d-aab7-b98ea16d490f
A8.1         write     /vm/0a3c1b35-33f8-432d-aab7-b98ea16d490f/name
debianhvm.guest.osstest
A8.1         write    
/local/domain/1/control/platform-feature-multiprocessor-suspend 1
A8.1         write    
/local/domain/1/control/platform-feature-xs_reset_watches 1
A8.1         commit
A8           write     /libxl/1/dm-version qemu_xen_traditional
A8.1         write     /local/domain/1/memory/static-max 5120000
A8.1         write     /local/domain/1/memory/target 5115904
A8.1         write     /local/domain/1/memory/videoram 4096
A8.1         write     /local/domain/1/domid 1

the logging shows that almost all details are identical, other than the
transaction ids on successive transactions.

Compiling oxenstored locally on my dev box (and in the XenServer build
system) confirms that transaction ids behave as intended, i.e. ids are
allocated incrementally, even with the identified changeset in place.

Where can I find the build logs for the bisection runs?  I am fairly
sure I have a newer version of Ocaml than comes by default in Debian,
and I wonder whether I have hit some version-dependent behaviour.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.