From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 1/4] tests: print reason when I/O test is skipped in TAP mode
Date: Wed, 8 Oct 2025 12:35:49 +0100 [thread overview]
Message-ID: <20251008113552.747002-2-berrange@redhat.com> (raw)
In-Reply-To: <20251008113552.747002-1-berrange@redhat.com>
The TAP output on a skipped test:
ok raw 181 # SKIP
is not informative.
The test program included a reason, and that should be displayed
in TAP mode (it is already shown in non-TAP mode):
ok raw 181 # SKIP Postcopy is not supported
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
tests/qemu-iotests/testrunner.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/testrunner.py b/tests/qemu-iotests/testrunner.py
index 14cc8492f9..c4ce3e29e9 100644
--- a/tests/qemu-iotests/testrunner.py
+++ b/tests/qemu-iotests/testrunner.py
@@ -174,7 +174,7 @@ def test_print_one_line(self, test: str,
elif status == 'fail':
print(f'not ok {self.env.imgfmt} {test}')
elif status == 'not run':
- print(f'ok {self.env.imgfmt} {test} # SKIP')
+ print(f'ok {self.env.imgfmt} {test} # SKIP {description}')
return
if lasttime:
--
2.50.1
next prev parent reply other threads:[~2025-10-08 11:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 11:35 [PATCH 0/4] tests: do more testing of block drivers in CI Daniel P. Berrangé
2025-10-08 11:35 ` Daniel P. Berrangé [this message]
2025-10-08 11:47 ` [PATCH 1/4] tests: print reason when I/O test is skipped in TAP mode Thomas Huth
2025-10-08 11:35 ` [PATCH 2/4] tests: rearrange suites for I/O tests Daniel P. Berrangé
2025-10-14 8:26 ` Kevin Wolf
2025-10-15 13:44 ` Daniel P. Berrangé
2025-10-15 13:47 ` Thomas Huth
2025-10-15 13:48 ` Daniel P. Berrangé
2025-10-08 11:35 ` [PATCH 3/4] tests: add nbd and luks to the I/O test suites Daniel P. Berrangé
2025-10-08 11:55 ` Thomas Huth
2025-10-08 12:55 ` Daniel P. Berrangé
2025-10-08 13:03 ` Thomas Huth
2025-10-08 15:55 ` Eric Blake
2025-10-14 8:50 ` Kevin Wolf
2025-10-14 20:19 ` Eric Blake
2025-10-08 15:49 ` Eric Blake
2025-10-08 11:35 ` [PATCH RFC/WIP 4/4] gitlab: add jobs for thorough block tests Daniel P. Berrangé
2025-10-08 15:57 ` Eric Blake
2025-10-08 16:23 ` Daniel P. Berrangé
2025-10-13 21:46 ` Eric Blake
2025-10-10 11:55 ` Thomas Huth
2025-10-10 12:11 ` Daniel P. Berrangé
2025-10-08 16:28 ` [PATCH 0/4] tests: do more testing of block drivers in CI 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=20251008113552.747002-2-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=hreitz@redhat.com \
--cc=kwolf@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 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).