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

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

On Thu, 2014-12-18 at 18:29 +0100, Dario Faggioli wrote:
> On Thu, 2014-12-18 at 16:10 +0100, Juergen Gross wrote:

> > So: Why can't you test cpupools on ARM?
> > 
> We certainly can. ARM testing via OSSTest is a still experimental,
> AFAIUI.

arm32 testing is production in osstest.

> I don't even know if we have the hardware, yet, as I think the "rack" of
> ARM dev board IanC was working on will be setup in the new testing COLO,
> rather than in current OSSTest pool of hardware (someone correct me if
> I'm wrong).

The new rack is to replace the existing h/w used in production, since
that can't be shipped to the colo for various reasons.

> 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.

That's not your problem, but if you could add the new test above the cut
that would be great. I'll sort out the other ones at some point.

Ian.