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 0/4] iotests: Selfish patches
Date: Fri, 17 May 2019 11:56:24 +0200 [thread overview]
Message-ID: <20190517095628.10119-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.
Patch 2 through 4 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.
Final note: The best thing would probably to skip the null-aio tests in
093/136 if there is no null-aio support. However, I didn’t get anything
to work: Annotating with @iotests.skip_if_unsupported() didn’t work
because the format name is a class instance attribute; and just
iotests.skipTest() didn’t work because that would print 's' characters
instead of '.' in the output (and emit the number of skipped tests), so
the comparison against the reference output fails... Which is why I
decided to just run the test with null-co then. That means that some
tests run twice with null-co (if there is no null-aio support), but
that’s not too bad. Just ugly.
Max Reitz (4):
iotests: Add -display none to the qemu options
iotests: Prefer null-co over null-aio
iotests: Test driver whitelisting in 093
iotests: Test driver whitelisting in 136
tests/qemu-iotests/093 | 22 +++++++++++++++-------
tests/qemu-iotests/136 | 17 +++++++++++++----
tests/qemu-iotests/245 | 2 +-
tests/qemu-iotests/check | 2 +-
4 files changed, 30 insertions(+), 13 deletions(-)
--
2.21.0
next reply other threads:[~2019-05-17 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 9:56 Max Reitz [this message]
2019-05-17 9:56 ` [Qemu-devel] [PATCH 1/4] iotests: Add -display none to the qemu options Max Reitz
2019-05-17 10:23 ` Thomas Huth
2019-05-17 10:30 ` Alex Bennée
2019-05-17 9:56 ` [Qemu-devel] [PATCH 2/4] iotests: Prefer null-co over null-aio Max Reitz
2019-05-17 9:56 ` [Qemu-devel] [PATCH 3/4] iotests: Test driver whitelisting in 093 Max Reitz
2019-05-17 11:00 ` Kevin Wolf
2019-05-17 11:44 ` Max Reitz
2019-05-17 9:56 ` [Qemu-devel] [PATCH 4/4] 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=20190517095628.10119-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).