From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
George Dunlap <dunlapg@umich.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)
Date: Thu, 17 May 2012 11:20:29 +0100 [thread overview]
Message-ID: <20404.53485.499407.372275@mariner.uk.xensource.com> (raw)
In-Reply-To: <1337164146.27824.84.camel@zakaz.uk.xensource.com>
Ian Campbell writes ("Re: [Xen-devel] "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL)"):
> On Wed, 2012-05-16 at 11:24 +0100, George Dunlap wrote:
> > On Wed, May 16, 2012 at 9:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > > I guess we could make the test harness detect which to use, or perhaps
> > > we should just put in a hidden alias command?
> >
> > Why do we need to detect which to use?
>
> For the benefit of the bisector when crossing this changeset.
>
> > I pci-list-assignable was
> > introduced in the 4.2 dev cycle, I believe (which is why I wasn't
> > worried about changing the name); was it backported to 4.1?
In the interests of expedience, I have simply changed the tester to
use the new name (well, pushed a change to the tester's staging tree
to do so). Bisection will not work if the tester tries to bisect the
pcipt job but I think it's unlikely we'll have another nonobvious
bisectable regression given that the /actual/ test never passes.
Ian.
next prev parent reply other threads:[~2012-05-17 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 7:12 [xen-unstable test] 12889: regressions - FAIL xen.org
2012-05-16 8:34 ` "xl pci-list-assignable" command not implemented (Was: Re: [xen-unstable test] 12889: regressions - FAIL) Ian Campbell
2012-05-16 10:24 ` George Dunlap
2012-05-16 10:29 ` Ian Campbell
2012-05-17 10:20 ` Ian Jackson [this message]
2012-05-17 10:22 ` Ian Jackson
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=20404.53485.499407.372275@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=dunlapg@umich.edu \
--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).