From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, edgar.iglesias@xilinx.com,
stefanha@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org,
qemu-trivial@nongnu.org, Jiri Pirko <jiri@resnulli.us>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-trivial] [PATCH v4] tests: Avoid non-portable 'echo -ARG'
Date: Tue, 8 Aug 2017 09:29:58 -0500 [thread overview]
Message-ID: <b3458a2d-3643-d69e-611f-3832ad8f24b4@redhat.com> (raw)
In-Reply-To: <20170808135407.GK4850@dhcp-200-186.str.redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2028 bytes --]
On 08/08/2017 08:54 AM, Kevin Wolf wrote:
> Am 03.07.2017 um 20:09 hat Eric Blake geschrieben:
>> POSIX says that backslashes in the arguments to 'echo', as well as
>> any use of 'echo -n' and 'echo -e', are non-portable; it recommends
>> people should favor 'printf' instead. This is definitely true where
>> we do not control which shell is running (such as in makefile snippets
>> or in documentation examples). But even for scripts where we
>> require bash (and therefore, where echo does what we want by default),
>> it is still possible to use 'shopt -s xpg_echo' to change bash's
>> behavior of echo. And setting a good example never hurts when we are
>> not sure if a snippet will be copied from a bash-only script to a
>> general shell script (although I don't change the use of non-portable
>> \e for ESC when we know the running shell is bash).
>>
>> +++ b/tests/multiboot/run_test.sh
>> @@ -26,7 +26,7 @@ run_qemu() {
>> local kernel=$1
>> shift
>>
>> - echo -e "\n\n=== Running test case: $kernel $@ ===\n" >> test.log
>> + printf %b "\n\n=== Running test case: $kernel $@ ===\n\n" >> test.log
>>
>> $QEMU \
>> -kernel $kernel \
>
> Not completely sure why, but this broke the test with whitespace changes
> like this:
>
> -=== Running test case: mmap.elf -m 1.1M ===
> +=== Running test case: mmap.elf -m1.1M ===
I guess that means I'm not regularly running tests/multiboot? Is it not
part of 'make check' or qemu-iotests?
Ah, I see the problem, and it's insidious. We're using "...$@...", but
want to be using "...$*...". $@ causes multiple arguments to be passed,
but printf %b is not concatenating those arguments; while $* uses only a
single argument. We didn't notice it with echo -e, because echo inserts
a space between multiple arguments, just as you'd get a space with $*.
Fix coming up.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-08 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 18:09 [Qemu-trivial] [PATCH v4] tests: Avoid non-portable 'echo -ARG' Eric Blake
2017-07-05 15:08 ` Max Reitz
2017-08-08 13:54 ` Kevin Wolf
2017-08-08 14:29 ` Eric Blake [this message]
2017-08-08 14:48 ` Kevin Wolf
2017-08-08 20:46 ` Eric Blake
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=b3458a2d-3643-d69e-611f-3832ad8f24b4@redhat.com \
--to=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=jiri@resnulli.us \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
/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).