From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, qemu-block@nongnu.org
Subject: [PATCH v2 0/4] make check-block a meson test
Date: Thu, 20 Jan 2022 12:35:59 +0100 [thread overview]
Message-ID: <20220120113603.276144-1-pbonzini@redhat.com> (raw)
This series makes "meson test" run the block layer tests, reporting
their outcome in the same way as the other TAP tests.
Based-on: <20211223183933.1497037-1-vsementsov@virtuozzo.com>
v1->v2: make qcow2 the "quick" test, skip on Windows
Paolo Bonzini (4):
scripts/mtest2make: add support for SPEED=thorough
build: make check-block a meson test
qemu-iotests: require at least an argument to check-block.sh
check-block: replace -makecheck with TAP output
meson.build | 5 ++--
scripts/mtest2make.py | 20 ++++++++++---
tests/Makefile.include | 16 ++---------
tests/check-block.sh | 45 +++++++++++++----------------
tests/meson.build | 1 +
tests/qemu-iotests/check | 6 ++--
tests/qemu-iotests/meson.build | 30 +++++++++++++++++++
tests/qemu-iotests/testenv.py | 30 +++++++++----------
tests/qemu-iotests/testrunner.py | 49 +++++++++++++++++---------------
9 files changed, 117 insertions(+), 85 deletions(-)
create mode 100644 tests/qemu-iotests/meson.build
--
2.33.1
next reply other threads:[~2022-01-20 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 11:35 Paolo Bonzini [this message]
2022-01-20 11:36 ` [PATCH v2 1/4] scripts/mtest2make: add support for SPEED=thorough Paolo Bonzini
2022-01-20 11:36 ` [PATCH v2 2/4] build: make check-block a meson test Paolo Bonzini
2022-01-20 11:36 ` [PATCH v2 3/4] qemu-iotests: require at least an argument to check-block.sh Paolo Bonzini
2022-01-20 11:36 ` [PATCH v2 4/4] check-block: replace -makecheck with TAP output Paolo Bonzini
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=20220120113603.276144-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--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).