Re: [Xen-devel] [xen-unstable bisection] complete test-amd64-i386-xl-qemuu-winxpsp3-vcpus1

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 01.03.17 at 06:37, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-i386-xl-qemuu-winxpsp3-vcpus1
> testid xen-boot
> 
> 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:  1a6e3220cc19b8705c27ca90dbc615270237f372
>   Bug not present: 0f72f9ba1f0586afac67bc88f35eba5cc26392cd
>   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/106286/ 
> 
> 
>   commit 1a6e3220cc19b8705c27ca90dbc615270237f372
>   Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
>   Date:   Thu Feb 2 12:51:39 2017 +0100

Was the bisector possibly misguided here? The history of the test
shows a pass of it on chardonnay1 on Feb 8, and the current
xen-boot failure of this test (just like others) is due to Daniel's
"efi: create new early memory allocator".

Jan


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