xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [OSSTEST PATCH 2/2] make-flight: create the vNUMA HVM test job
Date: Tue, 6 Oct 2015 09:23:55 +0100	[thread overview]
Message-ID: <1444119835.5302.34.camel@citrix.com> (raw)
In-Reply-To: <20151005164141.GM29124@zion.uk.xensource.com>

On Mon, 2015-10-05 at 17:41 +0100, Wei Liu wrote:
> On Mon, Oct 05, 2015 at 05:34:11PM +0100, Ian Jackson wrote:
> > Dario Faggioli writes ("[OSSTEST PATCH 2/2] make-flight: create the
> > vNUMA HVM test job"):
> > > as a variant of regular Debian HVM jobs.
> > > 
> > > For now, the vNUMA topology is just hardcoded
> > > here, and it is 4 vCPUs and 2 vNUMA nodes. How
> > > to split resources is left to the test
> > > implementation (right now, it is just evenly
> > > split them between the 2 virtual nodes).
> > 
> > The make-flight changes here seem reasonable.
> > 
> > > Note that we do not yet support save/restore
> > > and migration for vNUMA enabled guests, so
> > > this test will fail (and in fact, it's added
> > > to the non-blocking list).
> > 
> > However, this is wrong.  Instead, you should arrange for
> > ts-migrate-support-check to fail in this case.
> > 
> 
> My two cents.
> 
> We don't need to make ts-migrate-support-check fail. It is fine for the
> actual migration test to fail at the beginning as it won't block the
> push gate. It's conceivable that vNUMA guest will be able to migrate in
> the future. When that comes true, the actual migration test will pass.

I think the point was that if the migration tests fails then all subsequent
test steps won't get run at all (apart from leak check & log collection
etc).

Whereas if ts-migrate-support-check fails then the migrations will be
skipped and those other tests will be run.

Ian.

  reply	other threads:[~2015-10-06  8:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 23:17 [OSSTEST PATCH 0/2] Testcase for HVM vNUMA Dario Faggioli
2015-10-01 23:17 ` [OSSTEST PATCH 1/2] TestSupport.pm: allow creating vNUMA enabled HVM guest configs Dario Faggioli
2015-10-02 11:32   ` Wei Liu
2015-10-02 12:02     ` Dario Faggioli
2015-10-02 12:18       ` Wei Liu
2015-10-02 12:30         ` Dario Faggioli
2015-10-02 12:21       ` Wei Liu
2015-10-02 12:32         ` Dario Faggioli
2015-10-01 23:17 ` [OSSTEST PATCH 2/2] make-flight: create the vNUMA HVM test job Dario Faggioli
2015-10-05 16:34   ` Ian Jackson
2015-10-05 16:41     ` Wei Liu
2015-10-06  8:23       ` Ian Campbell [this message]
2015-10-06  8:33         ` Dario Faggioli
2015-10-06  9:03           ` Ian Campbell
2015-10-06  9:13             ` Dario Faggioli
2015-10-06  9:05           ` Wei Liu
2015-10-06  9:18             ` Ian Campbell
2015-10-09 14:42   ` Ian Campbell
2015-10-02  9:33 ` [OSSTEST PATCH 0/2] Testcase for HVM vNUMA Dario Faggioli
2015-10-02 10:15 ` Dario Faggioli
2015-10-02 11:40   ` Wei Liu

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=1444119835.5302.34.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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).