From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/5] iotests: Selfish patches
Date: Tue, 25 Jun 2019 23:19:50 +0200 [thread overview]
Message-ID: <20190625211955.15664-1-mreitz@redhat.com> (raw)
Hi,
These are some rather selfish iotests patches. The first patch helps me
personally because I tend to run the tests over SSH and forget to set
$DISPLAY. That makes test 139 skip the tests annotated with
skip_if_unsupprted(), because iotests.py can no longer determine the
list of whitelisted formats.
Patches 2 through 5 are specifically for RHEL. We have not whitelisted
null-aio, so it would be nice if tests didn’t require it. Sorry, I
don’t have a better reason to give.
In all seriousness, null-co is used widely in many tests, it basically
is our standard null driver. Tests should prefer it over null-aio, just
for consistency alone. It is not completely unreasonable to treat
null-aio as optional. I guess.
v2:
- Allow tests to use the unittest module’s skipTest() so it is possible
to skip a test case in the setUp() method (new patch 3). Then use
this in patches 4 and 5 to skip all null-aio cases instead of falling
back to null-co and thus running tests twice.
- Patch 1 needed to be rebased on
4a715461c8eab628e79b1e6889d650455e043b88
(“tests/qemu-iotests/check: Pick a default machine if necessary”)
git backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/5:[0008] [FC] 'iotests: Add -display none to the qemu options'
002/5:[----] [--] 'iotests: Prefer null-co over null-aio'
003/5:[down] 'iotests: Allow skipping test cases'
004/5:[0007] [FC] 'iotests: Test driver whitelisting in 093'
005/5:[0007] [FC] 'iotests: Test driver whitelisting in 136'
Max Reitz (5):
iotests: Add -display none to the qemu options
iotests: Prefer null-co over null-aio
iotests: Allow skipping test cases
iotests: Test driver whitelisting in 093
iotests: Test driver whitelisting in 136
tests/qemu-iotests/093 | 21 ++++++++++++++-------
tests/qemu-iotests/136 | 16 ++++++++++++----
tests/qemu-iotests/245 | 2 +-
tests/qemu-iotests/check | 6 +++---
tests/qemu-iotests/iotests.py | 20 ++++++++++++++++++--
5 files changed, 48 insertions(+), 17 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-25 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 21:19 Max Reitz [this message]
2019-06-25 21:19 ` [Qemu-devel] [PATCH v2 1/5] iotests: Add -display none to the qemu options Max Reitz
2019-06-26 10:36 ` Philippe Mathieu-Daudé
2019-06-25 21:19 ` [Qemu-devel] [PATCH v2 2/5] iotests: Prefer null-co over null-aio Max Reitz
2019-08-12 18:59 ` [Qemu-devel] [Qemu-block] " John Snow
2019-06-25 21:19 ` [Qemu-devel] [PATCH v2 3/5] iotests: Allow skipping test cases Max Reitz
2019-08-12 19:00 ` [Qemu-devel] [Qemu-block] " John Snow
2019-06-25 21:19 ` [Qemu-devel] [PATCH v2 4/5] iotests: Test driver whitelisting in 093 Max Reitz
2019-06-25 21:19 ` [Qemu-devel] [PATCH v2 5/5] iotests: Test driver whitelisting in 136 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=20190625211955.15664-1-mreitz@redhat.com \
--to=mreitz@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).