From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org, mreitz@redhat.com,
Ishani <chugh.ishani@research.iiit.ac.in>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] nbd: Fix iotests failure due to changed client error message
Date: Mon, 17 Jul 2017 13:33:28 -0500 [thread overview]
Message-ID: <b6dd33f6-50ad-7308-396e-8bbb88de3d5a@redhat.com> (raw)
In-Reply-To: <f6c0aba5-7406-5bd6-fd48-a0d09ebb050b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
On 07/17/2017 01:12 PM, John Snow wrote:
>
>
> On 07/17/2017 10:23 AM, Eric Blake wrote:
>> Commit 8ecaeae8 changed the way the client requests an NBD export,
>> and in the process also changed the resulting error message when
>> the export is not present, breaking a couple of iotests. The error
>> message is now directly given by the server (a failed NBD_OPT_GO)
>> instead of implied by the client (after exhausting NBD_OPT_LIST),
>> but looking at the testsuite changes, it proves worthwhile to
>> reword the error message to be slightly less verbose (as this is
>> one particular error message likely to be hit by a user).
>>
>> Note that the error message is now sensitive to which binary is
>> running the server as well as the client (since the expected
>> output is replaying a message received from the server); in
also depends on the server being new enough to understand NBD_OPT_GO.
I'll tweak the commit message before sending the pull request
>> general iotests are run on client and server from the same source
>> code base, but if it proves problematic in practice, we'll have
>> to tweak or sanitize the output somehow.
>>
>> Reported-by: Kevin Wolf <kwolf@redhat.com>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>
> Thanks, fixes it up for me.
>
> Tested-by: John Snow <jsnow@redhat.com>
> Reviewed-by: John Snow <jsnow@redhat.com>
Thanks; queued on my NBD branch:
git://repo.or.cz/qemu/ericb.git nbd
--
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-07-17 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 14:23 [Qemu-devel] [PATCH] nbd: Fix iotests failure due to changed client error message Eric Blake
2017-07-17 18:12 ` [Qemu-devel] [Qemu-block] " John Snow
2017-07-17 18:33 ` 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=b6dd33f6-50ad-7308-396e-8bbb88de3d5a@redhat.com \
--to=eblake@redhat.com \
--cc=chugh.ishani@research.iiit.ac.in \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).