From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL 3/8] tests/functional: Bump up arm_replay timeout
Date: Thu, 13 Mar 2025 09:01:27 +0100 [thread overview]
Message-ID: <20250313080132.1467625-4-thuth@redhat.com> (raw)
In-Reply-To: <20250313080132.1467625-1-thuth@redhat.com>
From: Peter Maydell <peter.maydell@linaro.org>
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>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20250310102830.3752440-1-peter.maydell@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/functional/meson.build | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/functional/meson.build b/tests/functional/meson.build
index e78560a9011..e181ed1ea57 100644
--- a/tests/functional/meson.build
+++ b/tests/functional/meson.build
@@ -34,6 +34,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,
--
2.48.1
next prev parent reply other threads:[~2025-03-13 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 8:01 [PULL 0/8] Fixes for functional tests Thomas Huth
2025-03-13 8:01 ` [PULL 1/8] docs: Rename default-configs to configs Thomas Huth
2025-03-13 8:01 ` [PULL 2/8] tests/functional: Require 'user' netdev for ppc64 e500 test Thomas Huth
2025-03-13 8:01 ` Thomas Huth [this message]
2025-03-13 8:01 ` [PULL 4/8] docs/system: Fix the information on how to run certain functional tests Thomas Huth
2025-03-13 8:01 ` [PULL 5/8] tests/functional/asset: Fail assert fetch when retries are exceeded Thomas Huth
2025-03-13 8:01 ` [PULL 6/8] tests/functional/asset: Verify downloaded size Thomas Huth
2025-03-13 8:01 ` [PULL 7/8] tests/functional/asset: Add AssetError exception class Thomas Huth
2025-03-13 8:01 ` [PULL 8/8] tests/functional: skip vulkan test if missing vulkaninfo Thomas Huth
2025-03-14 4:46 ` [PULL 0/8] Fixes for functional tests Stefan Hajnoczi
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=20250313080132.1467625-4-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.