From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
Xiao Guang Chen <chenxg@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mimu@linux.vnet.ibm.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC v4 2/6] qemu-iotests: qemu machine type support
Date: Thu, 05 Feb 2015 10:57:39 -0700 [thread overview]
Message-ID: <54D3AF13.8090102@redhat.com> (raw)
In-Reply-To: <54D37BBD.505@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On 02/05/2015 07:18 AM, Max Reitz wrote:
>> reference_machine="$source_iotests/$seq.$QEMU_DEFAULT_MACHINE.out"
>> + if [ -f $reference_machine ]; then
>
> Maybe this should be [ -f "$reference_machine" ]. I guess spaces in the
> directory name will break the qemu-iotests anyway, but there's no reason
> not to use quotes here.
Or, since the script explicitly required bash, use a bashism:
if [[ -f $reference_machine ]]; then
>> +export QEMU_DEFAULT_MACHINE=$($QEMU -machine ? | awk
>> '/(default)/{print $1}')
>
> Interesting that "-machine ?" works. I would have expected it needed to
> be "-machine \?".
Correct, you need quoting here to avoid accidental globbing.
>
> Apparently bash does not replace wildcard characters if there is no
> match (in contrast, zsh errors out in that case). Therefore, this only
> works as long as there is no single-character-named file in the
> directory where "check" is executed (test: "touch i; ./check").
bash and zsh chose different defaults, but both shells are configurable
in the other direction (you can tell zsh to turn off warnings; and
here's how to make bash balk at an unsuccessful glob: shopt -s failglob
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-02-05 17:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 3:44 [Qemu-devel] [PATCH RFC v4 0/6] Update tests/qemu-iotests failing cases for the s390 platform Xiao Guang Chen
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 1/6] qemu-iotests: run qemu with -nodefaults Xiao Guang Chen
2015-02-05 3:52 ` Fam Zheng
2015-02-05 5:52 ` chen xiao guang
2015-02-05 14:22 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 2/6] qemu-iotests: qemu machine type support Xiao Guang Chen
2015-02-05 14:18 ` Max Reitz
2015-02-05 17:57 ` Eric Blake [this message]
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 3/6] qemu-iotests: fix tests 067, 071 and 087 Xiao Guang Chen
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 4/6] qemu-iotests: s390x: fix test 041 Xiao Guang Chen
2015-02-05 14:26 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 5/6] qemu-iotests: s390x: fix test 051 Xiao Guang Chen
2015-02-05 15:11 ` Max Reitz
2015-02-09 8:06 ` chen xiao guang
2015-02-09 14:35 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 6/6] qemu-iotests: s390x: fix test 055 Xiao Guang Chen
2015-02-05 15:16 ` Max Reitz
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=54D3AF13.8090102@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=chenxg@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).