xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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 2/3] standalone: Check job status at end of run-job.
Date: Tue, 29 Sep 2015 10:37:48 +0100	[thread overview]
Message-ID: <1443519469-22866-2-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1443519444.16718.18.camel@citrix.com>

Check if the job passed and if not (so status is fail, broken, running
etc) then return an error.

This is convenient for scripting.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 standalone | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/standalone b/standalone
index 0a5d96f..e85457d 100755
--- a/standalone
+++ b/standalone
@@ -299,6 +299,11 @@ case $op in
 	OSSTEST_HOST_REUSE=$reuse \
 	OSSTEST_SIMULATE=$dryrun \
 	    with_logging logs/$flight/$job.log ./sg-run-job $job
+
+	status=`job_status $flight $job`
+	echo "$flight.$job status = $status" >&2
+	if [ "x$status" != xpass ] ; then exit 1; fi
+
 	;;
     run-test)
 	need_flight; need_host
-- 
2.5.3

  parent reply	other threads:[~2015-09-29  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  9:37 [PATCH OSSTEST 0/3] Misc standalone wrapper improvements Ian Campbell
2015-09-29  9:37 ` [PATCH OSSTEST 1/3] standalone: Add get-job-status to pick status out of standalone.db Ian Campbell
2015-09-29 14:04   ` Ian Jackson
2015-09-29 14:20     ` Ian Campbell
2015-09-29 15:02       ` Ian Jackson
2015-09-29  9:37 ` Ian Campbell [this message]
2015-09-29 14:04   ` [PATCH OSSTEST 2/3] standalone: Check job status at end of run-job Ian Jackson
2015-09-29  9:37 ` [PATCH OSSTEST 3/3] standalone: Rotate logs rather than clobbering them Ian Campbell
2015-09-29 14: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=1443519469-22866-2-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).