From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Daniel P . Berrangé" <berrange@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PATCH v3 15/16] tests/fp: Bump fp-test-mulAdd test timeout to 3 minutes
Date: Fri, 15 Dec 2023 08:03:56 +0100 [thread overview]
Message-ID: <20231215070357.10888-16-thuth@redhat.com> (raw)
In-Reply-To: <20231215070357.10888-1-thuth@redhat.com>
When running the tests in slow mode with --enable-debug on a very loaded
system, the fp-test-mulAdd test can take longer than 2 minutes. Bump the
timeout to three minutes to make sure it passes in such situations, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/fp/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fp/meson.build b/tests/fp/meson.build
index cbc17392d6..3b7fc63749 100644
--- a/tests/fp/meson.build
+++ b/tests/fp/meson.build
@@ -124,7 +124,7 @@ test('fp-test-mulAdd', fptest,
# no fptest_rounding_args
args: fptest_args +
['f16_mulAdd', 'f32_mulAdd', 'f64_mulAdd', 'f128_mulAdd'],
- suite: ['softfloat-slow', 'softfloat-ops-slow', 'slow'], timeout: 90)
+ suite: ['softfloat-slow', 'softfloat-ops-slow', 'slow'], timeout: 180)
executable(
'fp-bench',
--
2.43.0
next prev parent reply other threads:[~2023-12-15 7:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 7:03 [PATCH v3 00/16] tests: enable meson test timeouts to improve debuggability Thomas Huth
2023-12-15 7:03 ` [PATCH v3 01/16] qtest: bump min meson timeout to 60 seconds Thomas Huth
2023-12-15 7:03 ` [PATCH v3 02/16] qtest: bump migration-test timeout to 8 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 03/16] qtest: bump qom-test timeout to 15 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 04/16] qtest: bump npcm7xx_pwn-test timeout to 5 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 05/16] qtest: bump test-hmp timeout to 4 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 06/16] qtest: bump pxe-test timeout to 10 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 07/16] qtest: bump prom-env-test timeout to 6 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 08/16] qtest: bump boot-serial-test timeout to 3 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 09/16] qtest: bump qos-test timeout to 2 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 10/16] qtest: bump aspeed_smc-test timeout to 6 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 11/16] qtest: bump bios-table-test timeout to 9 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 12/16] tests/qtest: Bump the device-introspect-test timeout to 12 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 13/16] tests/unit: Bump test-aio-multithread test timeout to 2 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 14/16] tests/unit: Bump test-crypto-block test timeout to 5 minutes Thomas Huth
2023-12-15 7:03 ` Thomas Huth [this message]
2023-12-15 7:03 ` [PATCH v3 16/16] mtest2make: stop disabling meson test timeouts Thomas Huth
2023-12-15 18:10 ` [PATCH v3 00/16] tests: enable meson test timeouts to improve debuggability Alex Bennée
2024-01-23 16:50 ` Michael Tokarev
2024-01-23 17:08 ` Daniel P. Berrangé
2024-01-23 17:47 ` Thomas Huth
2024-01-23 20:51 ` Michael Tokarev
2024-01-23 21:23 ` Peter Maydell
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=20231215070357.10888-16-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--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).