From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] tests/functional/meson.build: Bump arm_aspeed_bletchley timeout
Date: Fri, 21 Mar 2025 19:34:45 +0100 [thread overview]
Message-ID: <e51a2f6c-cdf2-42bb-aa0e-3ef1a4332031@redhat.com> (raw)
In-Reply-To: <20250321155806.1888867-1-peter.maydell@linaro.org>
On 21/03/2025 16.58, Peter Maydell wrote:
> The arm_aspeed_bletchley timeout takes more than its
> current 120s timeout on a debug Rust config:
>
> $ time (cd build/rust; PYTHONPATH=../../python:../../tests/functional QEMU_TEST_QEMU_BINARY=./qemu-system-arm ./pyvenv/bin/python3 ../../tests/functional/test_arm_aspeed_bletchley.py)
> TAP version 13
> ok 1 test_arm_aspeed_bletchley.BletchleyMachine.test_arm_ast2600_bletchley_openbmc
> 1..1
>
> real 2m15.536s
> user 3m21.444s
> sys 0m11.558s
>
> Bump it up to 480s, same as arm_aspeed_rainier.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> tests/functional/meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
> index 96d28289279..0f8be30fe27 100644
> --- a/tests/functional/meson.build
> +++ b/tests/functional/meson.build
> @@ -26,7 +26,7 @@ test_timeouts = {
> 'arm_aspeed_witherspoon' : 120,
> 'arm_aspeed_ast2500' : 720,
> 'arm_aspeed_ast2600' : 1200,
> - 'arm_aspeed_bletchley' : 120,
> + 'arm_aspeed_bletchley' : 480,
> 'arm_aspeed_rainier' : 480,
> 'arm_bpim2u' : 500,
> 'arm_collie' : 180,
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2025-03-21 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 15:58 [PATCH] tests/functional/meson.build: Bump arm_aspeed_bletchley timeout Peter Maydell
2025-03-21 18: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=e51a2f6c-cdf2-42bb-aa0e-3ef1a4332031@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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).