From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell 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 Message-ID: <1443536435.16718.102.camel@citrix.com> References: <1443519444.16718.18.camel@citrix.com> <1443519469-22866-1-git-send-email-ian.campbell@citrix.com> <22026.39542.164075.529676@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <22026.39542.164075.529676@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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.