qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] tests/functional: Bump up arm_replay timeout
Date: Mon, 10 Mar 2025 11:34:09 +0100	[thread overview]
Message-ID: <55210662-b291-4cfc-a56a-82a1b4133694@redhat.com> (raw)
In-Reply-To: <20250310102830.3752440-1-peter.maydell@linaro.org>

On 10/03/2025 11.28, Peter Maydell wrote:
> On my machine the arm_replay test takes over 2 minutes to run
> in a config with Rust enabled and debug enabled:
> 
> $ time (cd build/rust ; PYTHONPATH=../../python:../../tests/functional
> QEMU_TEST_QEMU_BINARY=./qemu-system-arm ./pyvenv/bin/python3
> ../../tests/functional/test_arm_replay.py)
> TAP version 13
> ok 1 test_arm_replay.ArmReplay.test_cubieboard
> ok 2 test_arm_replay.ArmReplay.test_vexpressa9
> ok 3 test_arm_replay.ArmReplay.test_virt
> 1..3
> 
> real    2m16.564s
> user    2m13.461s
> sys     0m3.523s
> 
> Bump up the timeout to 4 minutes.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>   tests/functional/meson.build | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
> index 97c3f4ad4e9..608732bec63 100644
> --- a/tests/functional/meson.build
> +++ b/tests/functional/meson.build
> @@ -31,6 +31,7 @@ test_timeouts = {
>     'arm_orangepi' : 540,
>     'arm_quanta_gsj' : 240,
>     'arm_raspi2' : 120,
> +  'arm_replay' : 240,
>     'arm_tuxrun' : 240,
>     'arm_sx1' : 360,
>     'intel_iommu': 300,

Reviewed-by: Thomas Huth <thuth@redhat.com>



      reply	other threads:[~2025-03-10 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 10:28 [PATCH] tests/functional: Bump up arm_replay timeout Peter Maydell
2025-03-10 10:34 ` Thomas Huth [this message]

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=55210662-b291-4cfc-a56a-82a1b4133694@redhat.com \
    --to=thuth@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).