From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [OSSTEST PATCH 1/2] mfi-common: Do not set enable_livepatch on build-*-prev
Date: Thu, 1 Nov 2018 15:53:34 +0000 [thread overview]
Message-ID: <20181101155335.20138-1-ian.jackson@eu.citrix.com> (raw)
branch_wants_livepatch checks the current Xen version. We don't want
to try enabling livepatch on trees that don't have it. And for the
-prev build we care about forward migration etc., not about
livepatching the previous version.
Resulting changes (standalone-generate-dump-flight-runvars):
runvar removed: enable_livepatch=true
in jobs: build-amd64-prev build-i386-prev
in branches: xen-4.8-testing xen-4.9-testing xen-unstable
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
CC: Andrew Cooper <andrew.cooper3@citrix.com>
---
mfi-common | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mfi-common b/mfi-common
index c2866e93..7ad81162 100644
--- a/mfi-common
+++ b/mfi-common
@@ -380,7 +380,7 @@ create_build_jobs () {
# $REVISION_PREVXEN.
job_create_build build-$arch-prev build \
arch=$arch enable_xend=false enable_ovmf=$enable_prevovmf\
- enable_xsm=false $livepatch_runvars \
+ enable_xsm=false \
tree_xen=$TREE_XEN \
$RUNVARS $BUILD_RUNVARS $BUILD_XEN_RUNVARS $arch_runvars \
$hostos_runvars \
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-11-01 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:53 Ian Jackson [this message]
2018-11-01 15:53 ` [OSSTEST PATCH 2/2] mfi-common: Enable livepatch tests in 4.10 and 4.11 as intended (!) Ian Jackson
2018-11-01 15:58 ` Andrew Cooper
2018-11-01 16:04 ` Ian Jackson
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=20181101155335.20138-1-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=konrad.wilk@oracle.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).