All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH 2/2] Testing cpupools: recipe for it and job definition
Date: Thu, 18 Dec 2014 18:29:14 +0100	[thread overview]
Message-ID: <1418923754.10854.25.camel@Abyss.station> (raw)
In-Reply-To: <5492EE60.5090005@suse.com>


[-- Attachment #1.1: Type: text/plain, Size: 2260 bytes --]

On Thu, 2014-12-18 at 16:10 +0100, Juergen Gross wrote:
> On 12/18/2014 04:04 PM, Wei Liu wrote:
> > On Thu, Dec 18, 2014 at 04:00:12PM +0100, Juergen Gross wrote:
> >> On 12/18/2014 02:39 PM, Dario Faggioli wrote:
> >>> Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> >>> ---
> >>>   make-flight |   11 +++++++++++
> >>>   sg-run-job  |    6 ++++++
> >>>   2 files changed, 17 insertions(+)
> >>>
> >>> diff --git a/make-flight b/make-flight
> >>> index a91f256..ce02c89 100755
> >>> --- a/make-flight
> >>> +++ b/make-flight
> >>> @@ -266,6 +266,16 @@ do_credit2_tests () {
> >>>               $debian_runvars all_hostflags=$most_hostflags
> >>>   }
> >>>
> >>> +do_cpupools_tests () {
> >>> +  if [ $xenarch != amd64 -o $dom0arch != amd64 ]; then
> >>> +    return
> >>> +  fi
> >>
> >> Why can't you test cpupools on x86_64?
> >>
> >
> > Don't worry. That's the name used for 64 bit (be it amd or intel) in
> > OSSTest. :-)
> 
Exactly, it comes from the Debian arches names.

> Aargh. Some automatic filter in my brain translated this to arm64 :-)
> 
HeHe :-)

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

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

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.

I'll give it a shot for v2.

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

  reply	other threads:[~2014-12-18 17:29 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 [this message]
2014-12-19  9:48           ` Ian Campbell
2014-12-19 10:50             ` Dario Faggioli
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=1418923754.10854.25.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.