From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] iotests: Enable -d for Python non-unittest tests
Date: Thu, 1 Aug 2019 19:57:40 +0200 [thread overview]
Message-ID: <976a878d-0344-8cb6-aa4b-d8e540bb1eaf@redhat.com> (raw)
In-Reply-To: <20190801151744.798-3-kwolf@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 546 bytes --]
On 01.08.19 17:17, Kevin Wolf wrote:
> The part of iotests.main() that is related to the implementation of the
> debug option -d and enables QEMU and QMP logging is not only useful in
> tests that use the Python unittest framework, but also in tests that
> work by comparing with a reference output.
>
> Factor these parts out into iotests.init() and call it from the test
> cases that currently lack support for debug output.
How does this relate to
https://lists.nongnu.org/archive/html/qemu-block/2019-07/msg01212.html ?
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-01 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 15:17 [Qemu-devel] [PATCH 0/3] iotests: Test migration with filter nodes Kevin Wolf
2019-08-01 15:17 ` [Qemu-devel] [PATCH 1/3] iotests: Move migration helpers to iotests.py Kevin Wolf
2019-08-01 17:44 ` Max Reitz
2019-08-01 15:17 ` [Qemu-devel] [PATCH 2/3] iotests: Enable -d for Python non-unittest tests Kevin Wolf
2019-08-01 17:57 ` Max Reitz [this message]
2019-08-02 14:07 ` Kevin Wolf
2019-08-05 22:19 ` John Snow
2019-08-06 9:51 ` Kevin Wolf
2019-08-06 13:09 ` John Snow
2019-08-01 15:17 ` [Qemu-devel] [PATCH 3/3] iotests: Test migration with all kinds of filter nodes Kevin Wolf
2019-08-01 18:50 ` Max Reitz
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=976a878d-0344-8cb6-aa4b-d8e540bb1eaf@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.