From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v2 0/5] qemu-iotests: quality of life improvements
Date: Wed, 24 Mar 2021 16:17:03 +0100 [thread overview]
Message-ID: <ccc12713-51fa-ba77-af2a-e43e926c7aa7@redhat.com> (raw)
In-Reply-To: <20210323181928.311862-1-pbonzini@redhat.com>
On 23/03/2021 19:19, 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
>
> v1->v2: patches 1-2 are a rewrite of v1's patch 1
> moved print_env change to patch 4
> do not use argparse.REMAINDER
>
> Paolo Bonzini (5):
> qemu-iotests: do not buffer the test output
> qemu-iotests: allow passing unittest.main arguments to the test
> scripts
> qemu-iotests: move command line and environment handling from
> TestRunner to TestEnv
> qemu-iotests: let "check" spawn an arbitrary test command
> qemu-iotests: fix case of SOCK_DIR already in the environment
>
> tests/qemu-iotests/check | 15 +++++-
> tests/qemu-iotests/iotests.py | 78 +++++++++++++++++++-------------
> tests/qemu-iotests/testenv.py | 22 +++++++--
> tests/qemu-iotests/testrunner.py | 15 +-----
> 4 files changed, 81 insertions(+), 49 deletions(-)
>
I can confirm that this helps a lot when debugging tests.
Tested-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
next prev parent reply other threads:[~2021-03-24 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 18:19 [PATCH v2 0/5] qemu-iotests: quality of life improvements Paolo Bonzini
2021-03-23 18:19 ` [PATCH v2 1/5] qemu-iotests: do not buffer the test output Paolo Bonzini
2021-03-23 18:54 ` Vladimir Sementsov-Ogievskiy
2021-03-23 18:57 ` Vladimir Sementsov-Ogievskiy
2021-03-23 18:19 ` [PATCH v2 2/5] qemu-iotests: allow passing unittest.main arguments to the test scripts Paolo Bonzini
2021-03-23 19:02 ` Vladimir Sementsov-Ogievskiy
2021-03-23 19:17 ` Vladimir Sementsov-Ogievskiy
2021-03-23 21:22 ` Paolo Bonzini
2021-03-24 7:34 ` Vladimir Sementsov-Ogievskiy
2021-03-23 18:19 ` [PATCH v2 3/5] qemu-iotests: move command line and environment handling from TestRunner to TestEnv Paolo Bonzini
2021-03-23 18:19 ` [PATCH v2 4/5] qemu-iotests: let "check" spawn an arbitrary test command Paolo Bonzini
2021-03-23 19:12 ` Vladimir Sementsov-Ogievskiy
2021-03-23 21:20 ` Paolo Bonzini
2021-03-24 7:36 ` Vladimir Sementsov-Ogievskiy
2021-03-23 18:19 ` [PATCH v2 5/5] qemu-iotests: fix case of SOCK_DIR already in the environment Paolo Bonzini
2021-03-24 15:17 ` Emanuele Giuseppe Esposito [this message]
2021-03-25 18:15 ` [PATCH v2 0/5] qemu-iotests: quality of life improvements Max Reitz
2021-03-26 6:50 ` Paolo Bonzini
2021-03-26 13:40 ` 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=ccc12713-51fa-ba77-af2a-e43e926c7aa7@redhat.com \
--to=eesposit@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).