Re: [Xen-devel] [PATCH OSSTEST v3 3/3] Create a flight to test OpenStack with xen-unstable and libvirt

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Tue, 2015-10-13 at 12:02 +0100, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [PATCH OSSTEST v3 3/3] Create a flight to
> test OpenStack with xen-unstable and libvirt"):
> > On Thu, Oct 08, 2015 at 05:42:56PM +0100, Ian Jackson wrote:
> > > If we do want to just ignore this issue of the other trees, I do
> > > indeed see no particular reason to explicitly set all the runvars to
> > > master.
> > > 
> > > > I think we want a push gate just for the regression tracking, but
> > > > not
> > > > really for its own sake.
> > 
> > Yes, that is what I had in mind, testing OpenStack with tips of xen and
> > libvirt.
> > > 
> > > In that case we I think yes don't really need to push multiple
> > > branches.
> > 
> > I'll remove all those revision_* runvars.
> 
> Do you mean to remove the settings of them all to `master', or the
> code to honour them ?
> 
> The machinery in the ts-* script to honour revision_xyz and to set
> built_revision_xyz is useful because the bisector can use it to finger
> individual tress.

That all comes for free via build_clone I think, IOW Anthony would need to
go a good deal out of his way to not honour them I think.

> Unless, of course, you don't want to run the bisector on these tests.

I don't think we should rule it out.

Ian.

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