From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 2/5] cs-adjust-flight: Add job-status to report job stats
Date: Tue, 6 Oct 2015 15:56:24 +0100 [thread overview]
Message-ID: <1444143384.5302.209.camel@citrix.com> (raw)
In-Reply-To: <22035.56899.387780.489817@mariner.uk.xensource.com>
On Tue, 2015-10-06 at 15:44 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 2/5] cs-adjust-flight: Add job
> -status to report job stats"):
> > The return code of sg-run-job does not reflect the state of the job,
> > which is instead written to the database. For the benefit of running
> > tests in a loop until failure add a command to retrieve the status to
> > stdout.
> ...
> > +job_status() {
> > + flight=$1; shift
> > + job=$1; shift
> > +
> > + status=$(OSSTEST_CONFIG=$config \
> > + ./cs-adjust-flight $flight job-status $job)
> > + echo "$status"
> > +}
>
> This is rather odd. Why do you capture the value in a variable and
> then pass it to echo ? You could just let the job_status command
> print its output directly.
It was previously echo "${status#* }" (or something like that). I should
have changed it.
Ian.
next prev parent reply other threads:[~2015-10-06 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 14:34 [PATCH OSSTEST v3 0/5] Misc standalone wrapper improvements Ian Campbell
2015-10-05 14:35 ` [PATCH OSSTEST 1/5] cs-adjust-flight: `branch' command ought to be `branch-set' Ian Campbell
2015-10-06 14:41 ` Ian Jackson
2015-10-05 14:35 ` [PATCH OSSTEST 2/5] cs-adjust-flight: Add job-status to report job stats Ian Campbell
2015-10-06 14:44 ` Ian Jackson
2015-10-06 14:56 ` Ian Campbell [this message]
2015-10-05 14:35 ` [PATCH OSSTEST 3/5] standalone: Check job status at end of run-job Ian Campbell
2015-10-05 14:35 ` [PATCH OSSTEST 4/5] standalone: Make it possible to pass options to run-test Ian Campbell
2015-10-06 14:46 ` Ian Jackson
2015-10-06 14:59 ` Ian Campbell
2015-10-06 15:24 ` Ian Jackson
2015-10-06 15:35 ` Ian Campbell
2015-10-06 15:37 ` Ian Jackson
2015-10-05 14:35 ` [PATCH OSSTEST 5/5] standalone: Use fail() from mgi-common in most places Ian Campbell
2015-10-06 14:46 ` 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=1444143384.5302.209.camel@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).