From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, marcandre.lureau@redhat.com, hreitz@redhat.com,
vsementsov@virtuozzo.com, qemu-block@nongnu.org
Subject: Re: [RFC PATCH 0/4] Replace custom test harness with "meson test"
Date: Mon, 18 Oct 2021 19:55:06 +0200 [thread overview]
Message-ID: <e6b6d66a-e056-47dd-6b27-219a342a8138@redhat.com> (raw)
In-Reply-To: <310bb057-00f4-d5be-e855-775690a723a1@redhat.com>
On 18/10/21 11:51, Thomas Huth wrote:
>> * CTRL+C will only interrupt the longest running test. Pressing
>> CTRL+C repeatedly three times (which you would likely do anyway,
>> that's how things work) interrupts the whole run
>
> I tried this, and while hitting CTRL-C multiple times brought me back to
> the shell prompt, the remaining tests kept getting started in the
> background instead of getting stopped ... something is still fishy here,
> I think.
Ok, I checked that out. Looks like CTRL+C magic and "make -j" are
incompatible. :/ So this will have to wait a bit more, but in the
meanwhile people can already use "meson test" if they want.
>> * Right now "make check-block" only does a single test run just like
>> "../tests/check-block.sh", but it would be possible to add the
>> thorough
>> suite to "meson test --suite block" as well.
>
> The output of the iotests is also not optimal yet... when running "make
> check SPEED=slow", the iotests are run multiple times with different
> target image types, but each run prints the same "▶ 1/1 test 001 OK"
> etc. to the console, so it's hard to say which target type is currently
> exercised. Would it be possible to include the target image type here,
> e.g. something like:
Yes, that's trivial:
diff --git a/tests/qemu-iotests/testrunner.py
b/tests/qemu-iotests/testrunner.py
index 3ef14af1fa..45debc1928 100644
--- a/tests/qemu-iotests/testrunner.py
+++ b/tests/qemu-iotests/testrunner.py
@@ -163,11 +163,11 @@ def test_print_one_line(self, test: str,
starttime: str,
if self.tap:
if status == 'pass':
- print(f'ok test {test}')
+ print(f'ok {self.env.imgfmt} {test}')
elif status == 'fail':
- print(f'not ok test {test}')
+ print(f'not ok {self.env.imgfmt} {test}')
elif status == 'not run':
- print(f'ok test {test} # SKIP')
+ print(f'ok {self.env.imgfmt} {test} # SKIP')
return
if lasttime:
In fact, that's exactly what was printed in the non-TAP case. Thanks
for the feedback, even though it was bad! :)
Paolo
prev parent reply other threads:[~2021-10-18 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 10:07 [RFC PATCH 0/4] Replace custom test harness with "meson test" Paolo Bonzini
2021-10-15 10:07 ` [PATCH 1/4] build: use "meson test" as the test harness Paolo Bonzini
2021-10-15 10:07 ` [PATCH 2/4] build: make check-block a meson test Paolo Bonzini
2021-10-15 10:07 ` [PATCH 3/4] check-block: replace -makecheck with TAP output Paolo Bonzini
2021-10-15 10:07 ` [PATCH 4/4] configure: remove dead EXESUF variable Paolo Bonzini
2021-10-15 12:38 ` Philippe Mathieu-Daudé
2021-10-15 13:36 ` Paolo Bonzini
2021-10-15 14:23 ` Philippe Mathieu-Daudé
2021-10-18 9:51 ` [RFC PATCH 0/4] Replace custom test harness with "meson test" Thomas Huth
2021-10-18 17:55 ` Paolo Bonzini [this message]
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=e6b6d66a-e056-47dd-6b27-219a342a8138@redhat.com \
--to=pbonzini@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vsementsov@virtuozzo.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).