From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PATCH v3 3/4] iotests: Include QMP input in .out files
Date: Mon, 18 Nov 2019 18:37:29 +0100 [thread overview]
Message-ID: <9c9284a0-19a8-fc17-d20d-346c959f4578@redhat.com> (raw)
In-Reply-To: <20191114213415.23499-4-eblake@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1702 bytes --]
On 14.11.19 22:34, Eric Blake wrote:
> We generally include relevant HMP input in .out files, by virtue of
> the fact that HMP echoes its input. But QMP does not, so we have to
> explicitly inject it in the output stream (appropriately filtered to
> keep the tests passing), in order to make it easier to read .out files
> to see what behavior is being tested (especially true where the output
> file is a sequence of {'return': {}}).
>
> Suggested-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> tests/qemu-iotests/common.qemu | 9 ++++
> tests/qemu-iotests/085.out | 26 ++++++++++
> tests/qemu-iotests/094.out | 4 ++
> tests/qemu-iotests/095.out | 2 +
> tests/qemu-iotests/109.out | 88 ++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/117.out | 5 ++
> tests/qemu-iotests/127.out | 4 ++
> tests/qemu-iotests/140.out | 5 ++
> tests/qemu-iotests/141.out | 26 ++++++++++
> tests/qemu-iotests/143.out | 3 ++
> tests/qemu-iotests/144.out | 5 ++
> tests/qemu-iotests/153.out | 11 +++++
> tests/qemu-iotests/156.out | 11 +++++
> tests/qemu-iotests/161.out | 8 ++++
> tests/qemu-iotests/173.out | 4 ++
> tests/qemu-iotests/182.out | 8 ++++
> tests/qemu-iotests/183.out | 11 +++++
> tests/qemu-iotests/185.out | 18 +++++++
> tests/qemu-iotests/191.out | 8 ++++
> tests/qemu-iotests/200.out | 1 +
> tests/qemu-iotests/223.out | 19 ++++++++
> tests/qemu-iotests/229.out | 3 ++
> tests/qemu-iotests/249.out | 6 +++
> 23 files changed, 285 insertions(+)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-18 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 21:34 [PATCH v3 for-4.2 0/4] tests: More iotest 223 improvements Eric Blake
2019-11-14 21:34 ` [PATCH v3 1/4] iotests: Fix 173 Eric Blake
2019-11-14 21:34 ` [PATCH v3 2/4] iotests: Switch nbd tests to use Unix rather than TCP Eric Blake
2019-11-18 17:29 ` Max Reitz
2019-11-18 17:42 ` Eric Blake
2019-11-18 17:57 ` Eric Blake
2019-11-18 18:44 ` Max Reitz
2019-11-18 22:18 ` Eric Blake
2019-11-18 22:36 ` Eric Blake
2019-11-14 21:34 ` [PATCH v3 3/4] iotests: Include QMP input in .out files Eric Blake
2019-11-18 17:37 ` Max Reitz [this message]
2019-11-14 21:34 ` [PATCH v3 4/4] tests: More iotest 223 improvements 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=9c9284a0-19a8-fc17-d20d-346c959f4578@redhat.com \
--to=mreitz@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).