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 1/3] standalone: Add get-job-status to pick status out of standalone.db
Date: Tue, 29 Sep 2015 15:20:35 +0100 [thread overview]
Message-ID: <1443536435.16718.102.camel@citrix.com> (raw)
In-Reply-To: <22026.39542.164075.529676@mariner.uk.xensource.com>
On Tue, 2015-09-29 at 15:04 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 1/3] standalone: Add get-job-status
> to pick status out of standalone.db"):
> > 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.
>
> Maybe this would be better as a cs-* utility, useable on production
> instances too ?
Could do, although actually it turns out that the functionality in patch #2
(i.e. having standalone check the error) was the thing which I really
needed for what I was doing (scripting a loop running the job over and over
till it failed).
If cs-job-status still seems useful then I can certainly add that. I'd
probably keep the convenience wrapper in standalone unless you object.
Ian.
next prev parent reply other threads:[~2015-09-29 14:20 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 [this message]
2015-09-29 15:02 ` Ian Jackson
2015-09-29 9:37 ` [PATCH OSSTEST 2/3] standalone: Check job status at end of run-job Ian Campbell
2015-09-29 14:04 ` 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=1443536435.16718.102.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.