xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [OSSTEST PATCH 15/28] cr-daily-branch: Use mg-adjust-flight to have smoke tests reuse builds
Date: Tue, 22 Sep 2015 16:12:40 +0100	[thread overview]
Message-ID: <1442934764-8672-4-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1442934764-8672-1-git-send-email-ian.jackson@eu.citrix.com>

The smoke tests are for testing xen-unstable.  We want to avoid
building anything else.  So arrange to reuse previous builds by
calling mg-adjust-flight-makexrefs.

We rebuild libvirt too.  This is necessary because libvirt is built
against xen.git, and uses ABI-unstable APIs, so we need a libvirt
built against the right xen.git.  This means, for the smoke tests, we
need to build libvirt ourselves.  Currently this build seems to take
416 sends (from host allocation, which we - perhaps naively - hope
will be able to reuse the host from the just-finished build job).

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
---
v4: Keep build-amd64-libvirt too.
v3: Add a comment about the --blessings=real
v2: New patch
---
 cr-daily-branch |   12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/cr-daily-branch b/cr-daily-branch
index 141bce5..dd9c30a 100755
--- a/cr-daily-branch
+++ b/cr-daily-branch
@@ -276,7 +276,19 @@ if [ "x$NEW_REVISION" = "x$OLD_REVISION" ]; then
 fi
 
 $DAILY_BRANCH_PREMAKE_HOOK
+
 flight=`$makeflight $branch $xenbranch $OSSTEST_BLESSING "$@"`
+
+case $branch in
+xen-unstable-smoke)
+	./mg-adjust-flight-makexrefs -v $flight \
+		'!build-amd64 !build-amd64-libvirt !build-armhf build-*' \
+		--debug --branch=xen-unstable --blessings=real
+	# Even adhoc or play flights ought to reuse only real
+	# previous builds.
+	;;
+esac
+
 $DAILY_BRANCH_POSTMAKE_HOOK
 
 heading=tmp/$flight.heading-info
-- 
1.7.10.4

  parent reply	other threads:[~2015-09-22 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:12 [OSSTEST PATCH v4 00/28] xen.git#staging smoke tests Ian Jackson
2015-09-22 15:12 ` [OSSTEST PATCH 05/28] sg-report-flight: Better searching for used revisions Ian Jackson
2015-09-22 15:24   ` Ian Campbell
2015-09-22 15:12 ` [OSSTEST PATCH 14/28] Provide xen-unstable-smoke branch Ian Jackson
2015-09-22 15:29   ` Ian Campbell
2015-09-22 15:31     ` Ian Jackson
2015-09-22 15:12 ` Ian Jackson [this message]
2015-09-22 15:30   ` [OSSTEST PATCH 15/28] cr-daily-branch: Use mg-adjust-flight to have smoke tests reuse builds Ian Campbell
2015-09-22 15:32     ` Ian Jackson
2015-09-22 15:12 ` [OSSTEST PATCH 19/28] ts-debian-hvm-install: Defer preseed generation Ian Jackson
2015-09-22 15:31   ` Ian Campbell
2015-09-22 15:12 ` [OSSTEST PATCH 20/28] ts-debian-hvm-install: Cope with images containing only isolinux Ian Jackson
2015-09-22 15:32   ` Ian Campbell
2015-09-22 15:12 ` [OSSTEST PATCH 22/28] ts-debian-hvm-install: Do not create EFI partition if EFI not in use Ian Jackson
2015-09-22 15:32   ` Ian Campbell
2015-09-22 15:12 ` [OSSTEST PATCH 28/28] Executive: Delay releasing build host shares by 90s Ian Jackson
2015-09-22 15:34   ` 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=1442934764-8672-4-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.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).