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: "Radoslaw Biernacki" <rad@semihalf.com>,
	"Leif Lindholm" <leif.lindholm@oss.qualcomm.com>,
	"Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests/functional: Bump some arm test timeouts
Date: Fri, 21 Feb 2025 15:25:21 +0100	[thread overview]
Message-ID: <12ff6477-7cd5-4ada-b7a8-97a3add814c3@redhat.com> (raw)
In-Reply-To: <20250221140640.786341-1-peter.maydell@linaro.org>

On 21/02/2025 15.06, Peter Maydell wrote:
> On my local machine, for a debug build, sbsaref_alpine takes
> nearly 900s:
> 
> $ (cd build/x86 && ./pyvenv/bin/meson test --setup thorough --suite func-thorough func-aarch64-aarch64_sbsaref_alpine
> )
> 
> 1/1 qemu:func-thorough+func-aarch64-thorough+thorough / func-aarch64-aarch64_sbsaref_alpine
>                        OK 896.90s
> 
> arm_aspeed_rainier can also run close to its current timeout:
>   6/44 qemu:func-thorough+func-arm-thorough+thorough / func-arm-arm_aspeed_rainier
>                        OK 215.75s
> 
> and arm_aspeed_ast2500 and arm_aspeed_ast2600 can go over:
> 13/44 qemu:func-thorough+func-arm-thorough+thorough / func-arm-arm_aspeed_ast2600
>                        OK 792.94s
> 
> 27/44 qemu:func-thorough+func-arm-thorough+thorough / func-arm-arm_aspeed_ast2500
>                   TIMEOUT 480.01s
> 
> The sx1 test fails not on the overall meson timeout but on the
> 60 second timeout in some of the subtests.
> 
> Bump all these timeouts up a bit.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> This at least gets 'make -j4 check-functional' to passing for me
> for an arm/aarch64 debug build, apart from the gpu test hang which
> we're discussing in a different thread. Whole thing takes 25 mins...
> ---
>   tests/functional/meson.build     | 8 ++++----
>   tests/functional/test_arm_sx1.py | 6 +++---
>   2 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
> index b516d21cba1..effa31701cf 100644
> --- a/tests/functional/meson.build
> +++ b/tests/functional/meson.build
> @@ -15,16 +15,16 @@ test_timeouts = {
>     'aarch64_raspi4' : 480,
>     'aarch64_rme_virt' : 1200,
>     'aarch64_rme_sbsaref' : 1200,
> -  'aarch64_sbsaref_alpine' : 720,
> +  'aarch64_sbsaref_alpine' : 1200,

I wonder whether we should disable that test with @skipSlowTest() by 
default, since it's really very slow...?

Anyway, for this patch here:
Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2025-02-21 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 14:06 [PATCH] tests/functional: Bump some arm test timeouts Peter Maydell
2025-02-21 14:25 ` Thomas Huth [this message]
2025-02-21 15:29   ` 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=12ff6477-7cd5-4ada-b7a8-97a3add814c3@redhat.com \
    --to=thuth@redhat.com \
    --cc=leif.lindholm@oss.qualcomm.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rad@semihalf.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).