From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH OSSTEST v3 5/6] standalone: allow making a baseline flight.
Date: Thu, 15 May 2014 11:30:38 +0100 [thread overview]
Message-ID: <1400149839-8489-5-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1400149787.4386.29.camel@kazak.uk.xensource.com>
While there make the existing --lvextend argument actually work (by passing it
to getopt) and document both.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
standalone | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/standalone b/standalone
index 36f02ba..0f491c1 100755
--- a/standalone
+++ b/standalone
@@ -8,7 +8,7 @@ usage: standalone [operations] [options...]
Operations:
-* make-flight [cf] [BRANCH]
+* make-flight [cf,lvextendmax,baseline] [BRANCH]
Create a flight testing the named branch.
@@ -36,6 +36,8 @@ Options:
-h HOST, --host=HOST Test host
-r, --reuse Do not wipe test host (default)
-R, --noreuse, --noreinstall Wipe the test host (if job or test does so)
+--lvextendmax=GB Limit the size of the build logical volume
+--baseline Create a baseline flight instead of a tip flight
--help This message
@@ -55,7 +57,7 @@ if [ x$op = x--help ] ; then
exit 0
fi
-TEMP=$(getopt -o c:f:h:rR --long config:,flight:,host:,reuse,noreuse,reinstall,help -- "$@")
+TEMP=$(getopt -o c:f:h:rR --long config:,flight:,host:,reuse,noreuse,reinstall,lvextendmax:,baseline,help -- "$@")
eval set -- "$TEMP"
@@ -64,6 +66,7 @@ flight="standalone"
host=
reuse=1 # Don't blow away machines by default
lvextendmax=50 # Leave some LVM space free for running tests
+nobaseline=y
while true ; do
case "$1" in
@@ -73,6 +76,7 @@ while true ; do
-r|--reuse) reuse=1; shift 1;;
-R|--noreuse|--reinstall)reuse=0;shift 1;;
--lvextendmax)lvextendmax=$2; shift 2;;
+ --baseline)nobaseline=n; shift 1;;
--help) usage; exit 0;;
--) shift ; break ;;
*) echo "Internal error!" ; exit 1 ;;
@@ -163,7 +167,7 @@ case $op in
BUILD_LVEXTEND_MAX="$lvextendmax" \
OSSTEST_FLIGHT=$flight \
OSSTEST_CONFIG=$config \
- OSSTEST_NO_BASELINE=y \
+ OSSTEST_NO_BASELINE=$nobaseline \
with_logging logs/$flight/make-flight.log ./cr-daily-branch $@ $branch
;;
--
1.9.0
next prev parent reply other threads:[~2014-05-15 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 10:29 [PATCH OSSTEST v3 0/6] test mainline qemu and seabios branches Ian Campbell
2014-05-15 10:30 ` [PATCH OSSTEST v3 1/6] Add a flight to test qemu.org's ("mainline") master branch Ian Campbell
2014-05-16 17:16 ` Ian Jackson
2014-05-15 10:30 ` [PATCH OSSTEST v3 2/6] Add a flight to test seabios.org's " Ian Campbell
2014-05-16 17:17 ` Ian Jackson
2014-05-15 10:30 ` [PATCH OSSTEST v3 3/6] ts-xen-build: stash the Xen and SeaBIOS .config's Ian Campbell
2014-05-16 17:17 ` Ian Jackson
2014-05-15 10:30 ` [PATCH OSSTEST v3 4/6] ts-xen-build: Move Xen build tree from xen-unstable to just xen Ian Campbell
2014-05-16 17:17 ` Ian Jackson
2014-05-15 10:30 ` Ian Campbell [this message]
2014-05-16 17:18 ` [PATCH OSSTEST v3 5/6] standalone: allow making a baseline flight Ian Jackson
2014-05-15 10:30 ` [PATCH OSSTEST v3 6/6] sg-run-job: check for prerequisite builds when running build jobs Ian Campbell
2014-05-16 17:19 ` 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=1400149839-8489-5-git-send-email-ian.campbell@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).