From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
qemu-block@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v3 13/14] tests: add QEMU_TEST_IO_SKIP for skipping I/O tests
Date: Thu, 15 Jan 2026 16:47:55 +0000 [thread overview]
Message-ID: <20260115164756.799402-14-berrange@redhat.com> (raw)
In-Reply-To: <20260115164756.799402-1-berrange@redhat.com>
The nature of block I/O tests is such that there can be unexpected false
positive failures in certain scenarios that have not been encountered
before, and sometimes non-deterministic failures that are hard to
reproduce.
Before enabling the I/O tests as gating jobs in CI, there needs to be a
mechanism to dynamically mark tests as skipped, without having to commit
code changes.
This introduces the QEMU_TEST_IO_SKIP environment variable that is set
to a list of FORMAT-OR-PROTOCOL:NAME pairs. The intent is that this
variable can be set as a GitLab CI pipeline variable to temporarily
disable a test while problems are being debugged.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
docs/devel/testing/main.rst | 7 +++++++
tests/qemu-iotests/testrunner.py | 16 ++++++++++++++++
2 files changed, 23 insertions(+)
diff --git a/docs/devel/testing/main.rst b/docs/devel/testing/main.rst
index 797111009a..f779a64415 100644
--- a/docs/devel/testing/main.rst
+++ b/docs/devel/testing/main.rst
@@ -284,6 +284,13 @@ that are specific to certain cache mode.
More options are supported by the ``./check`` script, run ``./check -h`` for
help.
+If a test program is known to be broken, it can be disabled by setting
+the ``QEMU_TEST_IO_SKIP`` environment variable with a list of tests to
+be skipped. The values are of the form FORMAT-OR-PROTOCOL:NAME, the
+leading component can be omitted to skip the test for all formats and
+protocols. For example ``export QEMU_TEST_IO_SKIP="luks:149 185 iov-padding``
+will skip ``149`` for LUKS only, and ``185`` and ``iov-padding`` for all.
+
Writing a new test case
~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/tests/qemu-iotests/testrunner.py b/tests/qemu-iotests/testrunner.py
index dbe2dddc32..ecb5d4529f 100644
--- a/tests/qemu-iotests/testrunner.py
+++ b/tests/qemu-iotests/testrunner.py
@@ -145,6 +145,18 @@ def __init__(self, env: TestEnv, tap: bool = False,
self._stack: contextlib.ExitStack
+ self.skip = {}
+ for rule in os.environ.get("QEMU_TEST_IO_SKIP", "").split(" "):
+ rule = rule.strip()
+ if rule == "":
+ continue
+ if ":" in rule:
+ fmt, name = rule.split(":")
+ if fmt in ("", env.imgfmt, env.imgproto):
+ self.skip[name] = True
+ else:
+ self.skip[rule] = True
+
def __enter__(self) -> 'TestRunner':
self._stack = contextlib.ExitStack()
self._stack.enter_context(self.env)
@@ -251,6 +263,10 @@ def do_run_test(self, test: str) -> TestResult:
description='No qualified output '
f'(expected {f_reference})')
+ if f_test.name in self.skip:
+ return TestResult(status='not run',
+ description='Listed in QEMU_TEST_IO_SKIP')
+
args = [str(f_test.resolve())]
env = self.env.prepare_subprocess(args)
--
2.52.0
next prev parent reply other threads:[~2026-01-15 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 16:47 [PATCH v3 00/14] tests: do more testing of block drivers Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 01/14] Revert "python/aqmp: fix send_fd_scm for python 3.6.x" Daniel P. Berrangé
2026-01-20 18:32 ` John Snow
2026-01-15 16:47 ` [PATCH v3 02/14] tests: print reason when I/O test is skipped in TAP mode Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 03/14] tests: remove redundant meson suite for iotests Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 04/14] tests: ensure all qcow2 I/O tests are able to be run via make Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 05/14] scripts/mtest2make: ensure output has stable sorting Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 06/14] scripts/mtest2make: support optional tests grouping Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 07/14] tests: add a meson suite / make target per block I/O tests format Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 08/14] docs/devel/testing: expand documentation for 'make check-block' Daniel P. Berrangé
2026-01-15 16:47 ` [PATCH v3 09/14] tests: add nbd and luks to the I/O test suites Daniel P. Berrangé
2026-01-16 7:42 ` Thomas Huth
2026-01-15 16:47 ` [PATCH v3 10/14] tests: use 'driver' as collective term for either format or protocol Daniel P. Berrangé
2026-01-16 7:44 ` Thomas Huth
2026-01-15 16:47 ` [PATCH v3 11/14] tests: validate dmsetup result in test 128 Daniel P. Berrangé
2026-01-16 7:45 ` Thomas Huth
2026-01-15 16:47 ` [PATCH v3 12/14] tests: fix check for sudo access in LUKS I/O test Daniel P. Berrangé
2026-01-15 16:47 ` Daniel P. Berrangé [this message]
2026-01-15 16:47 ` [PATCH v3 14/14] gitlab: add jobs for thorough block tests Daniel P. Berrangé
2026-01-16 7:53 ` Thomas Huth
2026-01-16 9:49 ` Daniel P. Berrangé
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=20260115164756.799402-14-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.