All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>, ian.jackson@eu.citrix.com
Subject: Re: [PATCH OSSTEST v2] Stubdom test case
Date: Tue, 9 Jun 2015 11:36:35 +0100	[thread overview]
Message-ID: <1433846195.7108.536.camel@citrix.com> (raw)
In-Reply-To: <1433793268-2910-1-git-send-email-wei.liu2@citrix.com>

On Mon, 2015-06-08 at 20:54 +0100, Wei Liu wrote:
> Currently only QEMU traditional supports stubdom, so we only create
> 
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm
> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64
> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
> 
> Note that stubdom only supports serial='pty'. Piping serial to stderr
> causes stubdom to exit abnormally.
> 
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> ---
> Changes in v2:
> 1. Don't set stubdom runvar for every test case.

>From the list of runvars I don't think this happened correctly:

> +xen-unstable               test-amd64-amd64-xl-qemut-debianhvm-amd64             enable_stubdom              false
> +xen-unstable               test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm         enable_stubdom              false

etc etc

Also:

> +xen-unstable               test-amd64-amd64-xl-qemuu-debianhvm-amd64             enable_stubdom
> +xen-unstable               test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm         enable_stubdom
> +xen-unstable               test-amd64-amd64-xl-qemuu-ovmf-amd64                  enable_stubdom

I don't think is desired.

> +  stubdom_suffix="";
> +  if [ x$stubdom = xtrue ]; then
> +      stubdom_suffix="-stubdom"
> +  fi
> +
> +  job_create_test test-$xenarch$kern-$dom0arch-xl$qemuu_suffix$stubdom_suffix-$testname-amd64\
>      test-debianhvm xl $xenarch $dom0arch $qemuu_runvar \
>      enable_xsm=$xsm                             \
> +    enable_stubdom=$stubdom                     \

if [ x$stubdom != x ] ; then
        stubdom_runvar="enable_stubdom=$stubdom"
fi

Then just pass $stubdom_runvar to job_create_test, this arranges that
enable_stubdom is only set if a specific value is requested.

> +      for stubdom in true false ; do

for stubdom in true '' ; do

then arranges to pass the right things into the above. May need more or
less quoting when $stubdom is used now.

Ian.

  reply	other threads:[~2015-06-09 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 19:54 [PATCH OSSTEST v2] Stubdom test case Wei Liu
2015-06-09 10:36 ` Ian Campbell [this message]
2015-06-09 10:51   ` Wei Liu

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=1433846195.7108.536.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.