[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 132932: regressions - FAIL

Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 132932: regressions - 
> >>> On 06.02.19 at 17:10, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> > flight 132932 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/132932/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-amd64-amd64-pvgrub  7 xen-boot                fail REGR. vs. 
> > 132820
> Hmm, the log is full of
> (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = ...
> This can hardly be a result of the three commits in range here.
> Assuming this is recurring / reproducible, is there a way to set
> up a bisect starting from an older flight? Otoh looking at a
> successful test in an older flight I find in
> http://logs.test-lab.xenproject.org/osstest/logs/132575/test-amd64-amd64-xl-credit2/serial-joubertin0.log
> much the same, just that there the box came up.

This failure occured on joubertin1.  The joubertins were put into
service again yesterday after a long absence.  (The absence was due to
hardware trouble with the PDU etc. - not anything that would cause
this crash.)

So I think this is probably a host-specific crash.

The bisector has found a basis pass in 127489 and is working on it.
It has only just started.  In particular it has not yet repro'd either
the basis pass or the new failure, and right now it is doing some
rebuilds of old (expired) build artifacts to repro the basis pass.

Results will appear here:


and interim reports, or a report of a failure to bisect, will go to
the osstest-output mailing list under subjects like this:

  Subject: [xen-unstable bisection] 132970: testing 


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.