Re: [Xen-devel] [xen-4.2-testing test] 58817: FAIL [and 2 more messages]

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Jan Beulich writes ("Re: [Xen-devel] [xen-4.2-testing test] 58817: FAIL"):
> >>> On 22.06.15 at 08:54, <osstest@xxxxxxxxxxxxxxx> wrote:
> > flight 58817 xen-4.2-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/58817/ 
> > 
> > Failures and problems with tests :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  build-amd64-libvirt          3 host-install(3) broken in 58584 REGR. vs. 
> > 58411
> 
> This has been repeating for like half a dozen (or even more) flights.
> Why is this state not getting cleared, considering that all these
> newer flights were successful, and there were no other blocking
> failures?

The way to interpret this is to look for something which _passed_ in
the flight regarded as a problem.  In this case:

osstest service user writes ("[xen-4.2-testing test] 58817: FAIL"):
> flight 58817 xen-4.2-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/58817/
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-amd64-libvirt 3 host-install(3) broken in 58584 REGR. vs. 58411
> 
> Tests which are failing intermittently (not blocking):
...
>  test-amd64-amd64-xl-win7-amd64 16 guest-stop fail pass in 58584


So: the heisenbug compensator needed to justify the failure of
test-amd64-amd64-xl-win7-amd64 step guest-stop, and found a pass in
58584.  But 58584 is broken in other ways, and brokennesses aren't
regarded as justifiable (because they can cause other tests not to
run).

I think it would be better if the heisenbug compensator did not
consider flights with broken jobs.  But that's a reporting problem,
not a wrong push gate answer problem.


> And with that - will it ever clear?

Not unless we get lucky and that guest-stop passes.

Ian.

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