From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: [PATCH OSSTEST v2 0/4] Avoid running Linux on hosts for the given version lacks drivers
Date: Wed, 16 Sep 2015 12:47:27 +0100 [thread overview]
Message-ID: <1442404047.18856.51.camel@citrix.com> (raw)
As discussed in the thread at
http://lists.xen.org/archives/html/xen-devel/2015-09/msg01067.html some
older versions of Linux lack drivers for hardware in some of our test
hosts, meaning in particular that the linux-3.4 branch is now stuck trying
to run all of its jobs on hosts which linux-3.4.y cannot possibly work on
and for which a backported driver is thought unlikely right now.
Fix this by introducing support to the resource allocator for filtering
candidates based on resource properties, which will be used specifically to
filter hosts by their LinuxKernelMin property.
Before applying this the following new host properties should be added:
./mg-hosts setprops chardonnay\* -- LinuxKernelMin 3.8
./mg-hosts setprops huxelrebe\* -- LinuxKernelMin 3.5
(strictly speaking chardonnay is actually fixed by 3.7-rc1).
The first patch was just for debugging, via the script attached to v1 and
some spurious host properties added in Cambridge. This could be dropped...
The full diff of ./standalone-generate-dump-flight-runvars is huge, a
representative hunk after sorting both files is:
@@ -501,7 +501,7 @@
linux-3.0 build-i386-xsm tree_qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
linux-3.0 build-i386-xsm tree_seabios
linux-3.0 build-i386-xsm tree_xen git://xenbits.xen.org/xen.git
-linux-3.0 test-amd64-amd64-amd64-pvgrub all_hostflags arch-amd64,arch-xen-amd64,suite-jessie,purpose-test
+linux-3.0 test-amd64-amd64-amd64-pvgrub all_hostflags arch-amd64,arch-xen-amd64,suite-jessie,purpose-test,PropMinVer:LinuxKernelMin:3.0
linux-3.0 test-amd64-amd64-amd64-pvgrub arch amd64
linux-3.0 test-amd64-amd64-amd64-pvgrub buildjob build-amd64
linux-3.0 test-amd64-amd64-amd64-pvgrub debian_arch amd64
This only occurs for linux-X.Y and not for other branches (including not
for non-numeric linux-FOO):
$ diff -u before-min-linux after-min-linux | grep ^[+-][^+-]| cut -f1 -d\ | sort | uniq
-linux-3.0
+linux-3.0
-linux-3.10
+linux-3.10
-linux-3.14
+linux-3.14
-linux-3.16
+linux-3.16
-linux-3.18
+linux-3.18
-linux-3.4
+linux-3.4
-linux-4.1
+linux-4.1
Ian.
next reply other threads:[~2015-09-16 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 11:47 Ian Campbell [this message]
2015-09-16 11:47 ` [PATCH OSSTEST v2 1/4] ts-hosts-allocate-Executive: Allow dry-run Ian Campbell
2015-09-16 11:47 ` [PATCH OSSTEST v2 2/4] ts-hosts-allocate-Executive: add a label to loop over candidates Ian Campbell
2015-09-16 11:47 ` [PATCH OSSTEST v2 3/4] Add support for selecting resources based on their properties Ian Campbell
2015-09-16 13:50 ` Ian Jackson
2015-09-16 13:58 ` Ian Campbell
2015-09-16 14:00 ` Ian Jackson
2015-09-16 14:07 ` Ian Campbell
2015-09-16 11:47 ` [PATCH OSSTEST v2 4/4] make-flight: Add a minimum linux version requirement to all linux-* branches Ian Campbell
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=1442404047.18856.51.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).