From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/5] iotests.py: Add qemu_io_silent
Date: Mon, 30 Apr 2018 11:40:23 -0500 [thread overview]
Message-ID: <eea123af-ec17-beb5-74b6-0fd81d22e138@redhat.com> (raw)
In-Reply-To: <20180428144123.30333-5-mreitz@redhat.com>
On 04/28/2018 09:41 AM, Max Reitz wrote:
> With qemu-io now returning a useful exit code, some tests may find it
> sufficient to just query that instead of logging (and filtering) the
> whole output.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> tests/qemu-iotests/iotests.py | 9 +++++++++
> 1 file changed, 9 insertions(+)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-04-30 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 14:41 [Qemu-devel] [PATCH 0/5] qemu-io: Exit with error when a command failed Max Reitz
2018-04-28 14:41 ` [Qemu-devel] [PATCH 1/5] qemu-io: Drop command functions' return values Max Reitz
2018-04-30 14:58 ` Eric Blake
2018-04-28 14:41 ` [Qemu-devel] [PATCH 2/5] qemu-io: Let command functions return error code Max Reitz
2018-04-30 15:08 ` Eric Blake
2018-04-30 15:14 ` Max Reitz
2018-04-28 14:41 ` [Qemu-devel] [PATCH 3/5] qemu-io: Exit with error when a command failed Max Reitz
2018-04-30 16:38 ` Eric Blake
2018-04-28 14:41 ` [Qemu-devel] [PATCH 4/5] iotests.py: Add qemu_io_silent Max Reitz
2018-04-30 16:40 ` Eric Blake [this message]
2018-04-28 14:41 ` [Qemu-devel] [PATCH 5/5] iotests: Let 216 make use of qemu-io's exit code Max Reitz
2018-04-30 16:44 ` 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=eea123af-ec17-beb5-74b6-0fd81d22e138@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).