From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Paul Durrant <xadimgnik@gmail.com>
Subject: [OSSTEST PATCH 4/4] make-flight: Test Xen 4.9 and Xen 4.10 on stretch
Date: Tue, 16 Jun 2020 17:58:12 +0100 [thread overview]
Message-ID: <20200616165812.25380-4-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20200616165812.25380-1-ian.jackson@eu.citrix.com>
Xen 4.9 doesn't build on buster and won't be fixed for that.
Xen 4.10's "-prev" migration tests also fail for the same reason.
There is a (smallish) risk that Debian will break stretch before Xen
4.10 goes completely out of support from the Xen Project. If that
happens we could revert this - but then the 4.10 -prev jobs will stop
building.
Xen 4.9 is nearly out of security support, so for the 4.9 tests this
is a no-brainer.
I have checked the runvar diff. The results are to change
all_host_di_version [*]
all_host_suite
all_hostflags
debian_suite
debianhvm_suite
host_hostflags
in many jobs in
qemu-upstream-4.9-testing
qemu-upstream-4.10-testing
xen-4.9-testing
xen-4.10-testing
[*] this is not visible in standalone-generate-dump-flight-runvars
because it always just uses `current'.
This command produces no output:
diff -ub a <(perl -pe 's/stretch/buster/g' c)
(where `a' is before and `c' is after.)
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
make-flight | 2 ++
1 file changed, 2 insertions(+)
diff --git a/make-flight b/make-flight
index a361bcb1..836bc31c 100755
--- a/make-flight
+++ b/make-flight
@@ -41,6 +41,8 @@ case "$xenbranch" in
xen-4.1-testing) defsuite="wheezy"; defguestsuite="wheezy";;
xen-4.2-testing) defsuite="wheezy"; defguestsuite="wheezy";;
xen-4.3-testing) defsuite="wheezy"; defguestsuite="wheezy";;
+ xen-4.9-testing) defsuite="stretch"; defguestsuite="stretch";;
+ xen-4.10-testing) defsuite="stretch"; defguestsuite="stretch";;
*)
defsuite=`getconfig DebianSuite`
defguestsuite=`getconfig GuestDebianSuite`
--
2.20.1
prev parent reply other threads:[~2020-06-16 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 16:58 [OSSTEST PATCH 1/4] standalone: Fix spurious ] Ian Jackson
2020-06-16 16:58 ` [OSSTEST PATCH 2/4] standalone-generate-dump-flight-runvars: mkdir -p logs Ian Jackson
2020-06-16 16:58 ` [OSSTEST PATCH 3/4] standalone: Do not complain about ssh if AP_FETCH_PLACEHOLDERS=y Ian Jackson
2020-06-16 16:58 ` Ian Jackson [this message]
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=20200616165812.25380-4-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xadimgnik@gmail.com \
--cc=xen-devel@lists.xenproject.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).