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>
Subject: [OSSTEST PATCH 11/11] mg-repro-setup: Use --progress-fd
Date: Tue, 18 Apr 2017 16:56:52 +0100	[thread overview]
Message-ID: <1492531012-14315-12-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1492531012-14315-1-git-send-email-ian.jackson@eu.citrix.com>

Also, print a sensible message if allocation fails.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
 mg-repro-setup | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/mg-repro-setup b/mg-repro-setup
index af679d0..0b3137a 100755
--- a/mg-repro-setup
+++ b/mg-repro-setup
@@ -48,6 +48,8 @@ badusage () { echo >&2 "bad usage"; usage >&2; exit 126; }
 
 set -e -o posix
 
+. ./mgi-common
+
 mgexecflags=()
 adjustsets=()
 adjusts=()
@@ -171,9 +173,11 @@ progress "new flight is $flight"
 if [ "${alloc_idents[*]}" ]; then
 	progress "allocating ${alloc_idents[*]} ..."
 	alloc_output=tmp/$flight.allocations
-	./mg-allocate --stdout-output >$alloc_output $duration 2>&3 \
+	./mg-allocate \
+		--stdout-output >$alloc_output 5>&2 --progress-fd=5 2>&3 \
 		--info-base="[repro] $flight.$job $testid" \
-		"${alloc_specs[@]}"
+		$duration "${alloc_specs[@]}" ||
+                fail "allocation failed."
 	exec <$alloc_output
 	progressf "allocated"
 	for ident in ${alloc_idents[*]}; do
@@ -201,6 +205,7 @@ if $skipcapture; then adjrunvar skip_testids "capture-logs*"; fi
 progress "executing ..."
 
 OSSTEST_NOALLOCATE=1 \
-./mg-execute-flight -B$blessing -f$refflight "${mgexecflags[@]}" $flight
+./mg-execute-flight -B$blessing -f$refflight --progress-fd=2 \
+	"${mgexecflags[@]}" $flight
 
 progress "complete (see tmp/$flight.*)"
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      parent reply	other threads:[~2017-04-18 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 15:56 [OSSTEST PATCH 00/11] Coverity fix and mg-repro-setup improvements Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 01/11] TestSupport: Provide stashfilecontents Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 02/11] ts-coverity-upload: Pass HttpsProxyMITMCert to curl Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 03/11] truncation: Support globs, and multiple patterns Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 04/11] sg-run-job: Break out testid_matches_globs Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 05/11] sg-run-job: Start step a bit later Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 06/11] sg-run-job: Honour skip_testids runvar Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 07/11] mg-repro-setup: skip log capture (by default) Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 08/11] mg-allocate: Document --info-base in head comment Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 09/11] mg-allocate: Support --progress-fd Ian Jackson
2017-04-18 15:56 ` [OSSTEST PATCH 10/11] mg-execute-flight: " Ian Jackson
2017-04-18 15:56 ` 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=1492531012-14315-12-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.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).