All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 1/3] cs-adjust-flight: Add job-status to report job stats
Date: Mon, 5 Oct 2015 14:53:24 +0100	[thread overview]
Message-ID: <1444053204.5302.6.camel@citrix.com> (raw)
In-Reply-To: <22034.21862.669291.965109@mariner.uk.xensource.com>

On Mon, 2015-10-05 at 11:48 +0100, Ian Jackson wrote:
> > +    });
> > +}
> 
> This output format is awkward, isn't it ?
> 
> Would it be too horrible to omit `$job ' if the spec was a literal and
> can therefore only match one item ?  You can test that with something
> like
>     print "$job " or die $! if defined spec_re($jobs);

Yes I can make this work I think.

I wasn't too sure about having the output differ depending on the
parameters like this, but I think it probably is best.

> > +	*)
> > +	    echo >&2 "ERROR: $status"
> > +	    exit 1
> 
> Do we not have `fail' in scope ?

It doesn't look like it, the script doesn't source anything at all so
there's certainly no path to mgi-common. The rest of the script is already
doing explicit echo + exit. I could tack on a cleanup.

>   Also TBH I'm not sure you need to be
> this careful anyway...

Belt and braces ;-)

> > +	if [ $# -ne 1 ] ; then
> > +	    echo "get-job-status: Need job" >&2
> > +	    exit 1
> 
> `fail' again ?
> 
> Ian.

  reply	other threads:[~2015-10-05 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 12:05 [PATCH OSSTEST v2 0/3] Misc standalone wrapper improvements Ian Campbell
2015-10-02 12:05 ` [PATCH OSSTEST v2 1/3] cs-adjust-flight: Add job-status to report job stats Ian Campbell
2015-10-05 10:48   ` Ian Jackson
2015-10-05 13:53     ` Ian Campbell [this message]
2015-10-02 12:05 ` [PATCH OSSTEST v2 2/3] standalone: Check job status at end of run-job Ian Campbell
2015-10-02 12:05 ` [PATCH OSSTEST v2 3/3] standalone: Make it possible to pass options to run-test Ian Campbell
2015-10-05 10:50   ` Ian Jackson
2015-10-05 13:47     ` Ian Campbell

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=1444053204.5302.6.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.