Re: [Xen-devel] [OSSTEST PATCH RFC] do not install xend for xl tests

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2013-12-18 at 14:56 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[OSSTEST PATCH RFC] do not install xend for xl tests"):
> > We need to check that xl works correctly when xend is not even installed (in
> > case we are subtly relying on some file which xend installs).
> > 
> > Therefore for xen 4.4 onwards never build xend in the default build job and
> > instead create two new build jobs (for i386 and amd64) with xend enabled.
> > Update the tests to use the correct xenbuildjob.
> > 
> > Tested only to the extent of running make-flight for
> > xen-4.{2,3,4}-testing and xen-unstable and observing that the jobs
> > do not differ for 4.2 and 4.3 and the 4.4 and unstable have gained
> > the new build-{i386,and64}-xend jobs and that the relevant tests
> > have switched their xenbuildjob runvar to have the suffix.
> 
> Can we solve this problem by having a variant of "make install" which
> provides a differentiated output ?  That way we could use the same
> build, split into several outputs.

I suppose anything is possible/ASMOP ;-) But it seems like it would
involve a lot of fiddly build system stuff which would only ever be
exercised by osstest.

What I really want is for the non-xend test cases to be using the same
build environment as what end users will be using by default, which
doesn't involve a split make install (e.g. what if we get a critical
file in the wrong list?).

Ian.


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