Re: [OSSTEST PATCH 2/2] Testing cpupools: recipe for it and job definition

[Ian Campbell <Ian.Campbell@citrix.com>]

On Fri, 2014-12-19 at 11:50 +0100, Dario Faggioli wrote:
> > > However, that seems to be taken into account by the fact that, in
> > > make-flight, in test_matrix_do_one(), after only 2 jobs are created (the
> > > basic debian one and a libvirt one) we have this:
> > > 
> > >   # No further arm tests at the moment
> > >   if [ $dom0arch = armhf ]; then
> > >       return
> > >   fi
> > > 
> > > So, yes, I guess I can get rid of such filters in my new function, so
> > > that, when ARM maintainers  will disable the safety catch above, a job
> > > will actually be generated.
> > 
> > We should probably move some of the tests from below the cut to above
> > already, e.g. do_sedf_tests and do_credit2_tests aren't arch specific,
> > so should be run on arm.
> > 
> I see. Great. :-)
> 
> Scheduler testing being below the cutoff was exactly what made me
> thinking that we only wanted basic ARM testing for now, given the
> limited HW resources, and to keep the "noise" low

Actually if anything we are underutilising the ARM resources we have,
they usually finish way in advance of all the x86 stuff.

Ian.