From: Paolo Bonzini <pbonzini@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: eesposit@redhat.com, vsementsov@virtuozzo.com, qemu-block@nongnu.org
Subject: Re: [PATCH v3 0/5] qemu-iotests: quality of life improvements
Date: Tue, 30 Mar 2021 13:52:06 +0200 [thread overview]
Message-ID: <aadda300-ab72-292b-8d25-419ae934bfbc@redhat.com> (raw)
In-Reply-To: <a6b0d60c-af40-a16c-8c97-c00348984d98@redhat.com>
On 30/03/21 13:44, Max Reitz wrote:
> On 30.03.21 13:32, Max Reitz wrote:
>> On 26.03.21 15:23, Paolo Bonzini wrote:
>>> This series adds a few usability improvements to qemu-iotests, in
>>> particular:
>>>
>>> - arguments can be passed to Python unittests scripts, for example
>>> to run only a subset of the test cases (patches 1-2)
>>>
>>> - it is possible to do "./check -- ../../../tests/qemu-iotests/055
>>> args..."
>>> and specify arbitrary arguments to be passed to a single test script.
>>> This allows to take advantage of the previous feature and ease
>>> debugging
>>> of Python tests.
>>>
>>> Paolo
>> Thanks, I’ve amended patch 4 and applied the series to my block branch:
>>
>> https://git.xanclic.moe/XanClic/qemu/commits/branch/block
>
> I’m sorry but I’ll have to drop it again. At least iotests 245 und 295
> fail; I assume it has something to do with `iotests.activate_logging()`.
Ok, will look into it. Can you give me the exact set of ./check
invocations that you use?
Paolo
prev parent reply other threads:[~2021-03-30 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 14:23 [PATCH v3 0/5] qemu-iotests: quality of life improvements Paolo Bonzini
2021-03-26 14:23 ` [PATCH v3 1/5] qemu-iotests: do not buffer the test output Paolo Bonzini
2021-03-26 14:23 ` [PATCH v3 2/5] qemu-iotests: allow passing unittest.main arguments to the test scripts Paolo Bonzini
2021-03-26 14:23 ` [PATCH v3 3/5] qemu-iotests: move command line and environment handling from TestRunner to TestEnv Paolo Bonzini
2021-03-26 14:23 ` [PATCH v3 4/5] qemu-iotests: let "check" spawn an arbitrary test command Paolo Bonzini
2021-03-26 15:05 ` Max Reitz
2021-03-30 10:38 ` Max Reitz
2021-03-30 10:44 ` Max Reitz
2021-03-30 10:57 ` Max Reitz
2021-03-30 11:12 ` Paolo Bonzini
2021-03-26 14:23 ` [PATCH v3 5/5] qemu-iotests: fix case of SOCK_DIR already in the environment Paolo Bonzini
2021-03-30 11:32 ` [PATCH v3 0/5] qemu-iotests: quality of life improvements Max Reitz
2021-03-30 11:44 ` Max Reitz
2021-03-30 11:52 ` Paolo Bonzini [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=aadda300-ab72-292b-8d25-419ae934bfbc@redhat.com \
--to=pbonzini@redhat.com \
--cc=eesposit@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).