From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
thuth@redhat.com, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] meson: use thorough test setup as default
Date: Tue, 6 May 2025 10:36:06 +0100 [thread overview]
Message-ID: <aBnYBpAYjdgVpG8D@redhat.com> (raw)
In-Reply-To: <20250503201806.3045723-1-pierrick.bouvier@linaro.org>
On Sat, May 03, 2025 at 01:18:06PM -0700, Pierrick Bouvier wrote:
> Allows all tests to be visible by default when using meson test
> directly.
>
> This has no impact on make check-* commands, which use SPEED=quick by
> default (see scripts/mtest2make.py).
IMHO it would be conceptually confusing if we cause 'make check' to
be running different stuff from 'meson test'. As long as we keep a
makefile wrapper around running tests, I think we should keep them
matching what they do by default.
>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> meson.build | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index f8bf6e7bb66..57ff3f722d8 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -5,12 +5,13 @@ project('qemu', ['c'], meson_version: '>=1.5.0',
>
> meson.add_devenv({ 'MESON_BUILD_ROOT' : meson.project_build_root() })
>
> -add_test_setup('quick', exclude_suites: ['slow', 'thorough'], is_default: true,
> +add_test_setup('quick', exclude_suites: ['slow', 'thorough'],
> env: ['RUST_BACKTRACE=1'])
> add_test_setup('slow', exclude_suites: ['thorough'],
> env: ['G_TEST_SLOW=1', 'SPEED=slow', 'RUST_BACKTRACE=1'])
> add_test_setup('thorough',
> - env: ['G_TEST_SLOW=1', 'SPEED=thorough', 'RUST_BACKTRACE=1'])
> + env: ['G_TEST_SLOW=1', 'SPEED=thorough', 'RUST_BACKTRACE=1'],
> + is_default: true)
>
> meson.add_postconf_script(find_program('scripts/symlink-install-tree.py'))
>
> --
> 2.47.2
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-05-06 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 20:18 [PATCH] meson: use thorough test setup as default Pierrick Bouvier
2025-05-05 6:00 ` Paolo Bonzini
2025-05-05 17:32 ` Pierrick Bouvier
2025-05-05 10:32 ` Thomas Huth
2025-05-05 17:46 ` Pierrick Bouvier
2025-05-06 9:33 ` Daniel P. Berrangé
2025-05-06 15:31 ` Pierrick Bouvier
2025-05-06 15:36 ` Daniel P. Berrangé
2025-05-06 17:12 ` Thomas Huth
2025-05-07 7:14 ` Daniel P. Berrangé
2025-05-07 7:39 ` Thomas Huth
2025-05-07 18:45 ` Pierrick Bouvier
2025-05-08 10:05 ` Thomas Huth
2025-05-08 20:20 ` Pierrick Bouvier
2025-05-06 9:36 ` Daniel P. Berrangé [this message]
2025-05-06 10:16 ` 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=aBnYBpAYjdgVpG8D@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.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).