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] standalone: Extend -h to support ident=host style specifications
Date: Fri, 24 Jul 2015 14:51:19 +0100	[thread overview]
Message-ID: <1437745879.24746.107.camel@citrix.com> (raw)
In-Reply-To: <21938.16559.397508.847055@mariner.uk.xensource.com>

On Fri, 2015-07-24 at 14:42 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST] standalone: Extend -h to support 
> ident=host style specifications"):
> > Allowing for multi-host tests.
> ...
> >  	job=$1; shift
> > -	./cs-adjust-flight -v $flight runvar-del $job host
> > +	./cs-adjust-flight -v $flight runvar-del $job '/host$'
> 
> This regexp is slightly wrong because host runvars are all
>   (?:\w+_)?host$

I'll update.

> > +	    hosts="$ident=$h $hosts"
> 
> Any reason you push it on the front rather than adding it to the end ?

So that it matches the order of the arguments. Which matters for the run
-test case. At least it did for ts-guest-nbd-mirror which wants to be given
$srvhost $clthost in that order.

> It _shouldn't_ matter, but what if someone specifies -h foo=X -h foo=Y ?

For run-test ts-* will get foo=X foo=Y on the command line. For run-job
OSSTEST_HOST_FOO=X will prevail.

Perhaps export_hosts_environ should process the list in $hosts in reverse?
I think that gets best of both worlds?

Ian.

      reply	other threads:[~2015-07-24 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 12:56 [PATCH OSSTEST] standalone: Extend -h to support ident=host style specifications Ian Campbell
2015-07-24 13:42 ` Ian Jackson
2015-07-24 13:51   ` Ian Campbell [this message]

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