Re: [Xen-devel] [xen-4.4-testing test] 57474: tolerable trouble: blocked/broken/fail/pass - PUSHED

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 29.05.15 at 20:51, <osstest@xxxxxxxxxxxxxxx> wrote:
> flight 57474 xen-4.4-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/57474/ 
> 
> Failures :-/ but no regressions.
> 
> Tests which are failing intermittently (not blocking):
>  test-armhf-armhf-xl-multivcpu  3 host-install(3)          broken pass in 
> 57411
>  test-armhf-armhf-xl-credit2   3 host-install(3)           broken pass in 
> 57411
>  test-amd64-i386-xl-qemuu-win7-amd64 14 guest-localmigrate.2 fail in 57411 
> pass in 57474
>  test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail pass in 
> 57411

So this issue is visible on 4.4 too (the earlier flight 57411 also
suggests so). Interestingly the two 4.5 flights that completed over
the weekend do not display it (but there's no reason to believe it's
gone). Is this perhaps tied to a particular host? If so, would it be
possible to set up a custom bisection on just that host? If not,
would setting up a custom bisection taking into account the
randomness of the failure be an option?

Otoh hand the issue displaying even on 4.3 (which receives only
security updates, and whose QEMU_UPSTREAM_REVISION is still at
qemu-xen-4.3.4) should limit the set of possibly offending commits
quite drastically (unless of course this is an old issue that for some
reason started to surface now, or there was a qemuu specific
adjustment in osstest itself). Flight 50315 (Apr 4) testing
46ed0083a7 appears to be the first one (while earlier flights in
March have random test-amd64-i386-pair
guest-migrate/src_host/dst_host failures, aiui this is a PV migration
test and hence qemuu unrelated). Yet that commit to me doesn't
look at all like it would have the potential of introducing (random)
migration failures.

Jan


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