From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Juergen Gross <jgross@suse.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: [OSSTest PATCH v2 0/2] Test case for cpupools
Date: Wed, 4 Feb 2015 15:26:59 +0000 [thread overview]
Message-ID: <20150204152351.29118.60045.stgit@Abyss> (raw)
We aren't doing any cpupools smoke testing as of now. So, do some. :-)
As suggested by Juergen, I adjusted things such that we are now generating test
jobs for ARM too. In fact, here is the list of jobs, and for each jobs the
runvars, being introduced by this series:
dariof@hoopak:~/osstest.git$ diff -Nru runvars.orig runvars.patched
--- runvars.orig 2015-02-04 15:15:35.214928000 +0000
+++ runvars.patched 2015-02-04 15:11:30.529748000 +0000
@@ -0,0 +1,18 @@
+test-amd64-amd64-xl-cpupools all_hostflags arch-amd64,arch-xen-amd64,suite-wheezy,purpose-test
+test-amd64-amd64-xl-cpupools arch amd64
+test-amd64-amd64-xl-cpupools buildjob build-amd64
+test-amd64-amd64-xl-cpupools debian_arch amd64
+test-amd64-amd64-xl-cpupools debian_kernkind pvops
+test-amd64-amd64-xl-cpupools kernbuildjob build-amd64-pvops
+test-amd64-amd64-xl-cpupools kernkind pvops
+test-amd64-amd64-xl-cpupools toolstack xl
+test-amd64-amd64-xl-cpupools xenbuildjob build-amd64
+test-armhf-armhf-xl-cpupools all_hostflags arch-armhf,arch-xen-armhf,suite-wheezy,purpose-test
+test-armhf-armhf-xl-cpupools arch armhf
+test-armhf-armhf-xl-cpupools buildjob build-armhf
+test-armhf-armhf-xl-cpupools debian_arch armhf
+test-armhf-armhf-xl-cpupools debian_kernkind pvops
+test-armhf-armhf-xl-cpupools kernbuildjob build-armhf-pvops
+test-armhf-armhf-xl-cpupools kernkind pvops
+test-armhf-armhf-xl-cpupools toolstack xl
+test-armhf-armhf-xl-cpupools xenbuildjob build-armhf
Regards,
Dario
---
Dario Faggioli (2):
ts-cpupools: new test script
Testing cpupools: recipe for it and job definition
make-flight | 12 ++++++
sg-run-job | 7 +++
ts-cpupools | 124 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 143 insertions(+)
create mode 100755 ts-cpupools
--
<<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)
next reply other threads:[~2015-02-04 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:26 Dario Faggioli [this message]
2015-02-04 15:27 ` [OSSTest PATCH v2 1/2] ts-cpupools: new test script Dario Faggioli
2015-03-11 16:01 ` Ian Campbell
2015-02-04 15:28 ` [OSSTest PATCH v2 2/2] Testing cpupools: recipe for it and job definition Dario Faggioli
2015-03-11 16:02 ` Ian Campbell
2015-03-05 16:41 ` [OSSTest PATCH v2 0/2] Test case for cpupools Dario Faggioli
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=20150204152351.29118.60045.stgit@Abyss \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jgross@suse.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.