qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [RFC PATCH] tests/qemu-iotests: serialise all the qemu-iotests
Date: Wed, 22 Mar 2023 09:54:15 +0100	[thread overview]
Message-ID: <40ae1dd3-3061-603d-bb06-2bd71c54d4f9@linaro.org> (raw)
In-Reply-To: <20230321235102.3832417-1-alex.bennee@linaro.org>

On 22/3/23 00:51, Alex Bennée wrote:
> Something on OpenBSD fails with multiple tests running at once and
> fiddling with J=1 on invocation just made everything else very slow.
> 
> Based-on: 20230318114644.1340899-1-alex.bennee@linaro.org
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Daniel P. Berrangé <berrange@redhat.com>
> ---
>   tests/qemu-iotests/meson.build | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/tests/qemu-iotests/meson.build b/tests/qemu-iotests/meson.build
> index a162f683ef..d572205a60 100644
> --- a/tests/qemu-iotests/meson.build
> +++ b/tests/qemu-iotests/meson.build
> @@ -64,6 +64,7 @@ foreach format, speed: qemu_iotests_formats
>              depends: qemu_iotests_binaries,
>              env: qemu_iotests_env,
>              protocol: 'tap',
> +           is_parallel : false,

Per the commit description, what about:

               is_parallel: targetos != 'openbsd',

?

>              timeout: 180,
>              suite: suites)
>     endforeach



  reply	other threads:[~2023-03-22  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 23:51 [RFC PATCH] tests/qemu-iotests: serialise all the qemu-iotests Alex Bennée
2023-03-22  8:54 ` Philippe Mathieu-Daudé [this message]
2023-03-22  9:32 ` Daniel P. Berrangé
2023-03-22 10:21   ` Alex Bennée

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=40ae1dd3-3061-603d-bb06-2bd71c54d4f9@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).