Re: [Xen-devel] [OSSTest PATCH [RFC] 4/4] make-flight: Fedora guest tests

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Dario Faggioli writes ("Re: [OSSTest PATCH [RFC] 4/4] make-flight: Fedora guest 
tests"):
> On ven, 2013-12-13 at 16:49 +0000, Ian Jackson wrote:
> > This puts the Fedora arch name in the job name.  I think it would be
> > better if our job names used a consistent arch naming scheme (i.e.,
> > the Debian one).
> 
> You mean sticking with amd64 rather than x86_64? If yes, ok, I agree and
> that's easy enough.

Exactly, thanks.

> > According to your 0/4 message, this creates a large number of new test
> > jobs, but you're patching the ordinary make-flight.  So I think this
> > isn't really suitable as it is.
> > 
> So, the "lage number of new jobs" comes from the combination of Dom0
> arches and DomU arches, and from the fact that I'm testing two releases
> (19 and 20RC1, as per this series). I agree that all this variation is
> not necessary in regular flights, as I also tried to state myself in
> 0/4, so, yes, I think I can fall back to a less comprehensive set of
> test jobs, like only testing _one_ release, both amd64 and i386 for
> DomU, but only amd64 for dom0, like it is being done for the FreeBSD
> tests... Would this work?

Right.

> > Probably what we want is one or two extra jobs in the existing flights
> > (for testing new Xens still work with released Fedora) and a new more
> > comprehensive kind of flight for testing Fedora RCs.
> > 
> Ok, you mean (the final part) creating 'make-fedora-flight' with all and
> only the fedora jobs, right? Yes, I guess I can do that.

Perhaps.  I'm not sure whether it wants to be a different script or
not.  We already have some linux-specific flights which suppress most
of the jobs.  Maybe it would be better done with some ifs in the
existing script, or something.

If you do invent a make-fedora-flight you will have to factor out the
build parts of make-flight into a separate sub-script or a function in
a sourced file, or something.

Ian.

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