Xen devel - Oct 2013 - [qemu-upstream-unstable bisection] complete test-amd64-i386-qemuu-rhel6hvm-intel

[This email is either empty or too large to be displayed at this time]

On Sun, 2013-10-13 at 09:15 +0100, xen.org wrote:
> branch xen-unstable
> xen branch xen-unstable
> job test-amd64-i386-qemuu-rhel6hvm-intel
> test redhat-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/staging/qemu-xen-unstable.git
> Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> Tree: xen git://xenbits.xen.org/xen.git
> 
> *** Found and reproduced problem changeset ***
> 
>   Bug is in tree:  qemuu
git://xenbits.xen.org/staging/qemu-upstream-unstable.git
>   Bug introduced:  b97307ecaad98360f41ea36cd9674ef810c4f8cf
>   Bug not present: 4597594c61add43725bd207bb498268a058f9cfb
> 
> 
>   commit b97307ecaad98360f41ea36cd9674ef810c4f8cf
>   Author: Matthew Daley <mattjd@gmail.com>
>   Date:   Thu Oct 10 14:10:48 2013 +0000
>   
>       xen_disk: mark ioreq as mapped before unmapping in error case
I think the bisector has been confused by the upstream merge or
something because 4597594c61ad..b97307ecaad9 contains 5000+
changesets...

At least that means this security fix wasn''t obviously to blame!

The actual failure seems to be:
 test-amd64-i386-qemuu-rhel6hvm-intel  7 redhat-install    fail REGR. vs. 20054

which has happened in flight 20844 20840 and several earlier ones.

Logs don''t show anything especially thrilling though.

Ian.

On Sun, Oct 13, 2013 at 10:16:42AM +0100, Ian Campbell
wrote:
> On Sun, 2013-10-13 at 09:15 +0100, xen.org wrote:
> > branch xen-unstable
> > xen branch xen-unstable
> > job test-amd64-i386-qemuu-rhel6hvm-intel
> > test redhat-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/staging/qemu-xen-unstable.git
> > Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> > Tree: xen git://xenbits.xen.org/xen.git
> > 
> > *** Found and reproduced problem changeset ***
> > 
> >   Bug is in tree:  qemuu
git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> >   Bug introduced:  b97307ecaad98360f41ea36cd9674ef810c4f8cf
> >   Bug not present: 4597594c61add43725bd207bb498268a058f9cfb
> > 
> > 
> >   commit b97307ecaad98360f41ea36cd9674ef810c4f8cf
> >   Author: Matthew Daley <mattjd@gmail.com>
> >   Date:   Thu Oct 10 14:10:48 2013 +0000
> >   
> >       xen_disk: mark ioreq as mapped before unmapping in error case
> 
> I think the bisector has been confused by the upstream merge or
> something because 4597594c61ad..b97307ecaad9 contains 5000+
> changesets...
> 
> At least that means this security fix wasn''t obviously to blame!
> 
> The actual failure seems to be:
>  test-amd64-i386-qemuu-rhel6hvm-intel  7 redhat-install    fail REGR. vs.
20054
> 
> which has happened in flight 20844 20840 and several earlier ones.
> 
> Logs don''t show anything especially thrilling though.
To let you know, I''ve try to reproduce the test, but so far, the rhel
installation works as espected on my test machine (with 64bit and 32bit
dom0).

My next step was to try with a environment close to osstest, using
osstest-standalone.

Regards,

-- 
Anthony PERARD