From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PULL 2/8] hmp: Allow for error message hints on HMP
Date: Tue, 22 Sep 2015 19:02:10 -0400 [thread overview]
Message-ID: <5601DDF2.3060000@redhat.com> (raw)
In-Reply-To: <560189B3.6060602@redhat.com>
On 09/22/2015 01:02 PM, Eric Blake wrote:
> On 09/22/2015 09:23 AM, Kevin Wolf wrote:
>> Am 18.09.2015 um 15:22 hat Markus Armbruster geschrieben:
>>> From: Eric Blake <eblake@redhat.com>
>>>
>>> Commits 7216ae3d and d2828429 disabled some error message hints,
>>> all because a change to use modern error reporting meant that the
>>> hint would be output prior to the actual error. Fix this by making
>>> hints a first-class member of Error.
>>>
>>> For example, we are now back to the pleasant:
>>>
>>> $ qemu-system-x86_64 --nodefaults -S --vnc :0 --chardev null,id=,
>>> qemu-system-x86_64: --chardev null,id=,: Parameter 'id' expects an identifier
>>> Identifiers consist of letters, digits, '-', '.', '_', starting with a letter.
>>>
>>> Signed-off-by: Eric Blake <eblake@redhat.com>
>>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>>> Message-Id: <1441901956-21991-1-git-send-email-eblake@redhat.com>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>
>> This broke qemu-iotests 049. Can you please send a patch to update the
>> reference output?
>
> Will do (and I guess I should run qemu-iotests more frequently. Does
> 'make check' suffice, or is there other magic involved?)
>
>From the build directory:
pushd tests/qemu-iotests;
./check -v -qcow2;
./check -v -raw;
popd
If there is a smarter way of doing it, it is unknown to me.
--js
next prev parent reply other threads:[~2015-09-22 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 13:22 [Qemu-devel] [PULL 0/8] Error reporting patches Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 1/8] error: only prepend timestamp on stderr Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 2/8] hmp: Allow for error message hints on HMP Markus Armbruster
2015-09-22 15:23 ` Kevin Wolf
2015-09-22 17:02 ` Eric Blake
2015-09-22 23:02 ` John Snow [this message]
2015-09-18 13:22 ` [Qemu-devel] [PULL 3/8] error: Copy location information in error_copy() Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 4/8] MAINTAINERS: Add "Error reporting" entry Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 5/8] error: New error_fatal Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 6/8] Fix bad error handling after memory_region_init_ram() Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 7/8] loader: Fix memory_region_init_resizeable_ram() error handling Markus Armbruster
2015-09-18 13:22 ` [Qemu-devel] [PULL 8/8] memory: Fix bad error handling in memory_region_init_ram_ptr() Markus Armbruster
2015-09-18 15:57 ` [Qemu-devel] [PULL 0/8] Error reporting patches Peter Maydell
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=5601DDF2.3060000@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).