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-devel] [PATCH v4] tests: Avoid non-portable 'echo -ARG'
Date: Tue, 8 Aug 2017 15:46:20 -0500 [thread overview]
Message-ID: <7aa6c259-ccfe-a393-d89e-5727b8c12e90@redhat.com> (raw)
In-Reply-To: <20170808144800.GL4850@dhcp-200-186.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
On 08/08/2017 09:48 AM, Kevin Wolf wrote:
>>> 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?
>
> The problem is that it needs an i386 compiler to build the test kernels
> (and qemu-system-i386 or qemu-system-x86_64 binaries to execute them).
>
> I guess we could check these conditions, though, and skip the test if we
> can't produce i386 binaries.
And when you CAN run the test, it litters 'git status' of an in-tree
build with:
Untracked files:
(use "git add <file>..." to include in what will be committed)
tests/multiboot/mmap.elf
tests/multiboot/modules.elf
tests/multiboot/test.out
which ought to be fixed.
>
>> 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 $*.
>
> The thing that completely confused me here is that printf doesn't just
> ignore additional arguments as I would have expected, but just starts
> over with the format string, so that it does kind of work with multiple
> arguments and fails only subtly.
Both echo and printf accept more than one argument, but only echo
injects an automatic space between those arguments in the output.
--
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 --]
prev parent reply other threads:[~2017-08-08 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 18:09 [Qemu-devel] [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
2017-08-08 14:48 ` Kevin Wolf
2017-08-08 20:46 ` Eric Blake [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=7aa6c259-ccfe-a393-d89e-5727b8c12e90@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).