From: Hanna Reitz <hreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 3/4] tests/qemu-iotests: Move the bash and sanitizer checks to meson.build
Date: Mon, 21 Mar 2022 17:14:39 +0100 [thread overview]
Message-ID: <678cd508-fb61-4bd0-4d68-f1644f3baeb8@redhat.com> (raw)
In-Reply-To: <20220223093840.2515281-4-thuth@redhat.com>
On 23.02.22 10:38, Thomas Huth wrote:
> We want to get rid of check-block.sh in the long run, so let's move
> the checks for the bash version and sanitizers from check-block.sh
> into the meson.build file instead.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/check-block.sh | 26 --------------------------
> tests/qemu-iotests/meson.build | 14 ++++++++++++++
> 2 files changed, 14 insertions(+), 26 deletions(-)
FWIW
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
next prev parent reply other threads:[~2022-03-21 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:38 [PATCH v3 0/4] Improve integration of iotests in the meson test harness Thomas Huth
2022-02-23 9:38 ` [PATCH v3 1/4] tests/qemu-iotests: Rework the checks and spots using GNU sed Thomas Huth
2022-02-23 9:38 ` [PATCH v3 2/4] tests/qemu-iotests/meson.build: Improve the indentation Thomas Huth
2022-02-23 9:38 ` [PATCH v3 3/4] tests/qemu-iotests: Move the bash and sanitizer checks to meson.build Thomas Huth
2022-03-21 16:14 ` Hanna Reitz [this message]
2022-02-23 9:38 ` [PATCH v3 4/4] tests: Do not treat the iotests as separate meson test target anymore Thomas Huth
2022-02-24 14:03 ` [PATCH v3 0/4] Improve integration of iotests in the meson test harness Paolo Bonzini
2022-03-21 16:14 ` Hanna Reitz
2022-03-21 17:26 ` Thomas Huth
2022-03-23 11:33 ` Hanna Reitz
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=678cd508-fb61-4bd0-4d68-f1644f3baeb8@redhat.com \
--to=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=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 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.