Re: [xen-unstable test] 65141: regressions - FAIL

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

On Mon, 2015-11-30 at 05:35 +0000, Hu, Robert wrote:

Also adding Vt-x maintainers (Kevin and Jun) for their help/input, I'm not
sure if there is a dedicated nested-vmx maintainer. This failure has been
blocking the xen-unstable push gate for a week now so it really does need
looking into.

Also CC the arch X86 maintainers, for-their-info.

> > -----Original Message-----
> > From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> > Sent: Friday, November 27, 2015 11:54 PM
> > To: Hu, Robert <robert.hu@intel.com>
> > Cc: xen-devel@lists.xensource.com; osstest service owner
> > <osstest-admin@xenproject.org>
> > Subject: Re: [xen-unstable test] 65141: regressions - FAIL
> > 
> > osstest service owner writes ("[xen-unstable test] 65141: regressions -
> > FAIL"):
> > > flight 65141 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/65141/
> > > 
> > > Regressions :-(
> > > 
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > >  test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail
> > REGR. vs. 65114
> > 
> > Hi, Robert.  I hope you don't mind me asking you about these Nested
> > HVM tests in osstest production; if there's someone else we should
> > contact please let us know.
> [Hu, Robert] 
> 
> I'm trying to look for...
> But can I get the bad commit first?

It is in the original mail report, which is in the ML archives:
http://lists.xenproject.org/archives/html/xen-devel/2015-11/msg03222.html

version targeted for testing:
 xen                  b1d398b67781140d1c6efd05778d0ad4103b2a32
baseline version:
 xen                  713b7e4ef2aa4ec3ae697cde9c81d5a57548f9b1

You can also find it via the logs at
         http://logs.test-lab.xenproject.org/osstest/logs/65141
by clicking the header of one of the build-$arch jobs e.g. 
http://logs.test-lab.xenproject.org/osstest/logs/65141/build-amd64/info.html

and looking at the various tree_* and revision_* in the "Test control
variables" table, e.g.:
    revision_xen    	    b1d398b67781140d1c6efd05778d0ad4103b2a32    	    definition

> > Anyway: it seems this test failed just now.
> > 
> > osstest thinks it is a regression, but I think it is more likely that
> > this test either exhibits a heisenbug, or that there is some problem
> > which is specific to the particular host.

FWIW looking at the different branches in
 http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-qemuu-nested-intel/

While xen-unstable has started failing on godello1 xen-4.6-testing does
seem to be passing there.

The history for the previous job name (before splitting into -intel and
-amd) also shows a pass on godello1:

http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-qemuu-nested/xen-unstable.html

Of course this is a new test so there isn't very much historical data to
draw conclusions from.

> > We'd appreciate it if you and your colleagues could take a look at
> > this and analyse the failure.
> > 
> > In the meantime the osstest bisector will try to start work on it and
> > I will report what it discovers.

According to 
http://osstest.test-lab.xenproject.org/~osstest/pub/results/bisect/xen-unstable/test-amd64-amd64-qemuu-nested-intel.debian-hvm-install--l1--l2.html
it was unable to reproduce a baseline, probably because it didn't have
enough historical data. 

Ian.

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