From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Warner Losh" <imp@bsdimp.com>, "Ryo ONODERA" <ryoon@netbsd.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Kyle Evans" <kevans@freebsd.org>,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 07/11] tests/qemu-iotests: explicitly invoke 'check' via 'python'
Date: Thu, 30 Mar 2023 13:27:34 +0200 [thread overview]
Message-ID: <e279083e-f785-d64a-9464-30f95ffbc77d@redhat.com> (raw)
In-Reply-To: <20230330101141.30199-8-alex.bennee@linaro.org>
On 30/03/2023 12.11, Alex Bennée wrote:
> From: Daniel P. Berrangé <berrange@redhat.com>
>
> The 'check' script will use "#!/usr/bin/env python3" by default
> to locate python, but this doesn't work in distros which lack a
> bare 'python3' binary like NetBSD.
>
> We need to explicitly invoke 'check' by referring to the 'python'
> variable in meson, which resolves to the detected python binary
> that QEMU intends to use.
>
> This fixes a regression introduced by
>
> commit 51ab5f8bd795d8980351f8531e54995ff9e6d163
> Author: Daniel P. Berrangé <berrange@redhat.com>
> Date: Wed Mar 15 17:43:23 2023 +0000
>
> iotests: register each I/O test separately with meson
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Message-Id: <20230329124539.822022-1-berrange@redhat.com>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/qemu-iotests/meson.build | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/tests/qemu-iotests/meson.build b/tests/qemu-iotests/meson.build
> index a162f683ef..9735071a29 100644
> --- a/tests/qemu-iotests/meson.build
> +++ b/tests/qemu-iotests/meson.build
> @@ -47,19 +47,20 @@ foreach format, speed: qemu_iotests_formats
> endif
>
> rc = run_command(
> - [qemu_iotests_check_cmd] + args + ['-n'],
> + [python, qemu_iotests_check_cmd] + args + ['-n'],
> check: true,
> )
>
> foreach item: rc.stdout().strip().split()
> - args = ['-tap', '-' + format, item,
> + args = [qemu_iotests_check_cmd,
> + '-tap', '-' + format, item,
> '--source-dir', meson.current_source_dir(),
> '--build-dir', meson.current_build_dir()]
> # Some individual tests take as long as 45 seconds
> # Bump the timeout to 3 minutes for some headroom
> # on slow machines to minimize spurious failures
> test('io-' + format + '-' + item,
> - qemu_iotests_check_cmd,
> + python,
> args: args,
> depends: qemu_iotests_binaries,
> env: qemu_iotests_env,
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-03-30 11:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:11 [PATCH 00/11] more misc fixes for 8.0 (tests, gdbstub, meta, docs) Alex Bennée
2023-03-30 10:11 ` [PATCH 01/11] scripts/coverage: initial coverage comparison script Alex Bennée
2023-03-30 12:37 ` Thomas Huth
2023-03-30 10:11 ` [PATCH 02/11] gdbstub: Only build libgdb_user.fa / libgdb_softmmu.fa if necessary Alex Bennée
2023-03-30 10:11 ` [PATCH 03/11] MAINTAINERS: add a section for policy documents Alex Bennée
2023-03-30 11:24 ` Thomas Huth
2023-03-30 15:31 ` Markus Armbruster
2023-03-30 15:34 ` Warner Losh
2023-03-30 16:29 ` Kashyap Chamarthy
2023-04-03 7:56 ` Philippe Mathieu-Daudé
2023-03-30 10:11 ` [PATCH 04/11] qemu-options: finesse the recommendations around -blockdev Alex Bennée
2023-03-30 11:24 ` Thomas Huth
2023-04-01 8:00 ` Michael Tokarev
2023-04-03 6:22 ` Markus Armbruster
2023-04-03 13:16 ` Alex Bennée
2023-04-03 14:55 ` Markus Armbruster
2023-04-03 16:31 ` Thomas Huth
2023-04-03 18:17 ` Markus Armbruster
2023-03-30 10:11 ` [PATCH 05/11] metadata: add .git-blame-ignore-revs Alex Bennée
2023-03-30 11:25 ` Thomas Huth
2023-03-30 10:11 ` [PATCH 06/11] Use hexagon toolchain version 16.0.0 Alex Bennée
2023-03-30 10:11 ` [PATCH 07/11] tests/qemu-iotests: explicitly invoke 'check' via 'python' Alex Bennée
2023-03-30 11:27 ` Thomas Huth [this message]
2023-03-30 10:11 ` [PATCH 08/11] tests/vm: use the default system python for NetBSD Alex Bennée
2023-03-30 11:27 ` Thomas Huth
2023-03-30 10:11 ` [PATCH 09/11] tests/requirements.txt: bump up avocado-framework version to 101.0 Alex Bennée
2023-03-30 11:43 ` Thomas Huth
2023-03-30 12:12 ` Alex Bennée
2023-03-30 12:21 ` Thomas Huth
2023-03-31 7:50 ` Thomas Huth
2023-03-30 10:11 ` [PATCH 10/11] gitlab: fix typo Alex Bennée
2023-03-30 10:39 ` Philippe Mathieu-Daudé
2023-03-30 11:35 ` Thomas Huth
2023-03-30 10:11 ` [PATCH 11/11] tests/gitlab: use kaniko to build images Alex Bennée
2023-03-30 10:17 ` Daniel P. Berrangé
2023-03-30 10:49 ` Daniel P. Berrangé
2023-03-30 18:14 ` Alex Bennée
2023-03-30 12:35 ` Thomas Huth
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=e279083e-f785-d64a-9464-30f95ffbc77d@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=hreitz@redhat.com \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=ryoon@netbsd.org \
--cc=wainersm@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).