From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: [PATCH OSSTEST] ts-hosts-allocate-Standalone: abort if the host to use has changed
Date: Wed, 12 Feb 2014 11:10:51 +0000 [thread overview]
Message-ID: <1392203451-15422-1-git-send-email-ian.campbell@citrix.com> (raw)
When a job has been run once then the selected host is stored in a runvar and
used from then on. This means that if you try to run on a different host (by
changing the config or by changing OSSTEST_HOST_HOST) then you may be
surprised when things happen to the original host and not the new one.
Abort when this is detected.
Changing host requires you to run:
./cs-adjust-flight -v $flight runvar-del $job host
$flight = standalone by default
$job = test-x-y-z or build-x etc
host = the literal string host (not either of the host names)
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
ts-hosts-allocate-Standalone | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/ts-hosts-allocate-Standalone b/ts-hosts-allocate-Standalone
index 4ce0c0d..88a5d28 100755
--- a/ts-hosts-allocate-Standalone
+++ b/ts-hosts-allocate-Standalone
@@ -31,5 +31,13 @@ foreach my $ident (@ARGV) {
$host ||= $c{"TestHost_$ident"};
$host ||= $c{TestHost};
$host || die "need host setting for $ident";
+
+ my $expected = $ENV{'OSSTEST_HOST_'.uc $ident}
+ || $c{"TestHost_$ident"}
+ || $c{TestHost};
+
+ die "$ident configuration mismatch $r{$ident} != $expected"
+ if $r{$ident} && $r{$ident} ne $expected;
+
store_runvar($ident, $host);
}
--
1.8.5.2
next reply other threads:[~2014-02-12 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 11:10 Ian Campbell [this message]
2014-03-17 11:19 ` [PATCH OSSTEST] ts-hosts-allocate-Standalone: abort if the host to use has changed Ian Campbell
2014-03-17 11:32 ` 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=1392203451-15422-1-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).