xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: "Hu, Robert" <robert.hu@intel.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	"Jin, Gordon" <gordon.jin@intel.com>
Subject: Re: Nested HVM in xen-unstable tests
Date: Mon, 23 Nov 2015 10:04:10 +0000	[thread overview]
Message-ID: <1448273050.4973.23.camel@citrix.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD31023A3511@SHSMSX103.ccr.corp.intel.com>

On Sun, 2015-11-22 at 06:26 +0000, Hu, Robert wrote:
> > -----Original Message-----
> > From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> > Sent: Friday, November 20, 2015 10:46 PM
> > To: Hu, Robert <robert.hu@intel.com>
> > Cc: osstest service owner <osstest-admin@xenproject.org>; Jin, Gordon
> > <gordon.jin@intel.com>; xen-devel@lists.xensource.com
> > Subject: Nested HVM in xen-unstable tests
> > 
> > osstest service owner writes ("[xen-unstable test] 64750: regressions -
> > FAIL"):
> > > flight 64750 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/64750/
> > ...
> > >  test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail
> > baseline untested
> > 
> > It appears that this new test case is failing in xen-unstable.  The
> > logs are here:
> > 
> > 
> > http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64
> > -
> > qemuu-nested/info.html
> [Hu, Robert] 
> 
> Thanks Ian letting us know about this.
> Where can I find the related xen/qemu/dom0 kernel information?

At the bottom of the info.html page there is a table of "Test control
variables" which contains build *buildjob variables, those links take you
to the relevant build job. The info for those jobs then contains "Test
control variables" which include the trees and revisions of things built.

Also under "Logfiles etc." there is a "build/" subdirectory with the actual
binaries, and in the case of the kernbuildjob the kernel's .config.


> > If you would like to avoid this feature regressing, you probably want
> > to figure out what is wrong and send patches to fix it.  In the
> > meantime, the test will continue to fail in osstest but this will
> > not block pushes and will not impede anyone else's work.
> > 
> [Hu, Robert] 
> 
> I thought the test failure would block related patches getting accepted.

Osstest looks for regressions and blocks patches which introduce them,
however for there to be a regression then the test needs to have been
passing first.

Ian.

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

  reply	other threads:[~2015-11-23 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 22:39 [xen-unstable test] 64750: regressions - FAIL osstest service owner
2015-11-20 14:45 ` Nested HVM in xen-unstable tests Ian Jackson
2015-11-22  6:26   ` Hu, Robert
2015-11-23 10:04     ` Ian Campbell [this message]
2015-11-23 10:20   ` Ian Campbell
2015-11-23 10:49     ` [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel Ian Campbell
2015-11-23 11:27       ` Ian Jackson
2015-11-23 11:40       ` Ian Jackson
2015-11-25  5:32       ` Hu, Robert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1448273050.4973.23.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=gordon.jin@intel.com \
    --cc=osstest-admin@xenproject.org \
    --cc=robert.hu@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).