From: Thomas Huth <thuth@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: Hanna Reitz <hreitz@redhat.com>, qemu-devel@nongnu.org
Subject: [PATCH v2 0/3] tests/qemu-iotests: Improve test detection for meson
Date: Tue, 14 Oct 2025 12:41:39 +0200 [thread overview]
Message-ID: <20251014104142.1281028-1-thuth@redhat.com> (raw)
When running the test in thorough mode, we currently try to run a lot of
tests that are only skipped, which is somewhat annoying. This series
fixes the problems (see second patch), and add some more image formats
in the third patch (which should be fine now that the list of tests that
we try to execute is not that big anymore).
v2:
- Improve the detection mechanism in patch 2 by using regex statements
- Extend the comment in patch 2 a little bit, saying that the detection
can fail in certain cases, e.g. when the "unsupported_fmt" and the
"supported_fmt" statement are on the same line (which does not seem to
be a problem with the current test cases right now, fortunately)
Thomas Huth (3):
tests/qemu-iotests/184: Fix skip message for qemu-img without throttle
tests/qemu-iotests: Improve the dry run list to speed up thorough
testing
tests/qemu-iotest: Add more image formats to the thorough testing
tests/qemu-iotests/184 | 2 +-
tests/qemu-iotests/check | 42 +++++++++++++++++++++++++++++++---
tests/qemu-iotests/meson.build | 3 +++
3 files changed, 43 insertions(+), 4 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-14 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 10:41 Thomas Huth [this message]
2025-10-14 10:41 ` [PATCH v2 1/3] tests/qemu-iotests/184: Fix skip message for qemu-img without throttle Thomas Huth
2025-10-14 10:41 ` [PATCH v2 2/3] tests/qemu-iotests: Improve the dry run list to speed up thorough testing Thomas Huth
2025-10-14 10:41 ` [PATCH v2 3/3] tests/qemu-iotest: Add more image formats to the " Thomas Huth
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=20251014104142.1281028-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=hreitz@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).