From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 00/16] tests: enable meson test timeouts to improve debuggability
Date: Fri, 15 Dec 2023 18:10:30 +0000 [thread overview]
Message-ID: <87sf4372w9.fsf@draig.linaro.org> (raw)
In-Reply-To: <20231215070357.10888-1-thuth@redhat.com> (Thomas Huth's message of "Fri, 15 Dec 2023 08:03:41 +0100")
Thomas Huth <thuth@redhat.com> writes:
> This is a respin of Daniel's series that re-enables the meson test
> runner timeouts. To make sure that we do not get into trouble on
> older systems, I ran all the tests with "make check SPEED=slow -j32"
> on my laptop that has only 16 SMT threads, so each test was running
> quite a bit slower than with a normal "-j$(nproc)" run. I think
> that these timeouts should now work in most cases - if not, we still
> can adjust them easily later.
Queued to testing/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-12-15 18:11 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 ` [PATCH v3 15/16] tests/fp: Bump fp-test-mulAdd test timeout to 3 minutes Thomas Huth
2023-12-15 7:03 ` [PATCH v3 16/16] mtest2make: stop disabling meson test timeouts Thomas Huth
2023-12-15 18:10 ` Alex Bennée [this message]
2024-01-23 16:50 ` [PATCH v3 00/16] tests: enable meson test timeouts to improve debuggability 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=87sf4372w9.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).