From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@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 15:54:07 +0200 [thread overview]
Message-ID: <20170808135407.GK4850@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <20170703180950.9895-1-eblake@redhat.com>
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).
>
> Replace 'echo -n "..."' with 'printf %s "..."', and 'echo -e "..."'
> with 'printf %b "...\n"', with the optimization that the %s/%b
> argument can be omitted if the string being printed is a strict
> literal with no '%', '$', or '`' (we could technically also make
> this optimization when there are $ or `` substitutions but where
> we can prove their results will not be problematic, but proving
> that such substitutions are safe makes the patch less trivial
> compared to just being consistent).
>
> In the qemu-iotests check script, fix unusual shell quoting
> that would result in word-splitting if 'date' outputs a space.
>
> In test 051, take an opportunity to shorten the line.
>
> In test 068, get rid of a pointless second invocation of bash.
>
> CC: qemu-trivial@nongnu.org
> Signed-off-by: Eric Blake <eblake@redhat.com>
> diff --git a/tests/multiboot/run_test.sh b/tests/multiboot/run_test.sh
> index 78d7edf..c8f3da8 100755
> --- a/tests/multiboot/run_test.sh
> +++ 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 ===
Kevin
next prev parent reply other threads:[~2017-08-08 13:54 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 [this message]
2017-08-08 14:29 ` Eric Blake
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=20170808135407.GK4850@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=jiri@resnulli.us \
--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).