Re: [qemu-upstream-4.4-testing test] 62580: regressions - FAIL

[Ian Campbell <ian.campbell@citrix.com>]

On Mon, 2015-10-05 at 09:56 +0100, Ian Campbell wrote:
> On Sat, 2015-10-03 at 19:32 +0000, osstest service owner wrote:
> > flight 62580 qemu-upstream-4.4-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/62580/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-vhd        9 debian-di-install         fail REGR.
> > vs. 60565
> >  test-amd64-i386-xl-qcow2      9 debian-di-install         fail REGR.
> > vs. 60565
> 
> From:
> http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-upstream-
> 4.4-testing/test-amd64-i386-xl-vhd.debian-di-install.html
> and
> http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-upstream-
> 4.4-testing/test-amd64-i386-xl-qcow2.debian-di-install.html
> 
> It seems like it is unable to reproduce the baseline pass.
> 
> I think what has happened here is that these test cases have landed on
> merlot* and are waiting for "libxl: Increase device model startup timeout
> to 1min." which is currently in staging-4.4 (and seems to be stuck there,
> which is next on my list to investigate).
> 
> I think this justifies force pushing qemu-upstream-4.4-testing in the
> meantime.

In the end we decided (in "[xen-4.4-testing test] 62616: regressions -
FAIL") to force push xen-4.4-testing, meaning that the thing which is
blocking these qemu-upstream-4.4-testing runs will go away.

So no force push for this one, I am however about to kill flight 62675 so
we can get a replacement going on the new xen-4.4-testing baseline.

Ian.