From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH 2/2] Testing cpupools: recipe for it and job definition
Date: Fri, 19 Dec 2014 11:50:56 +0100 [thread overview]
Message-ID: <1418986256.10854.30.camel@Abyss.station> (raw)
In-Reply-To: <1418982526.20028.2.camel@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2167 bytes --]
On Fri, 2014-12-19 at 09:48 +0000, Ian Campbell wrote:
> 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.
>
Ok.
> > 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.
I'll certainly move this one below it.
> 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.
>
Sure I will.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-12-19 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 13:38 [OSSTEST PATCH 0/2] Test case for cpupools Dario Faggioli
2014-12-18 13:38 ` [OSSTEST PATCH 1/2] ts-cpupools: new test script Dario Faggioli
2014-12-18 14:57 ` Juergen Gross
2014-12-18 13:39 ` [OSSTEST PATCH 2/2] Testing cpupools: recipe for it and job definition Dario Faggioli
2014-12-18 15:00 ` Juergen Gross
2014-12-18 15:04 ` Wei Liu
2014-12-18 15:10 ` Juergen Gross
2014-12-18 17:29 ` Dario Faggioli
2014-12-19 9:48 ` Ian Campbell
2014-12-19 10:50 ` Dario Faggioli [this message]
2014-12-19 11:02 ` Ian Campbell
2014-12-18 13:44 ` [OSSTEST PATCH 0/2] Test case for cpupools Dario Faggioli
2014-12-18 14:56 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1418986256.10854.30.camel@Abyss.station \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jgross@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.