From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Cleber Rosa" <crosa@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 06/12] qtest: bump pxe-test timeout to 3 minutes
Date: Wed, 19 Jul 2023 15:08:57 +0200 [thread overview]
Message-ID: <b73807c7-ba19-9a22-ddf9-93b0fb2980a3@redhat.com> (raw)
In-Reply-To: <20230717182859.707658-7-berrange@redhat.com>
On 17/07/2023 20.28, Daniel P. Berrangé wrote:
> The pxe-test takes about 1 + 1/2 minutes in a --enable-debug
> build. Bumping to 3 minutes will give more headroom.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> tests/qtest/meson.build | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/qtest/meson.build b/tests/qtest/meson.build
> index 1070c6dc64..c6da428dc5 100644
> --- a/tests/qtest/meson.build
> +++ b/tests/qtest/meson.build
> @@ -4,6 +4,7 @@ slow_qtests = {
> 'npcm7xx_pwm-test': 300,
> 'qom-test' : 900,
> 'test-hmp' : 240,
> + 'pxe-test': 180,
> }
>
> qtests_generic = [
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-07-19 13:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 18:28 [PATCH v2 00/12] tests: enable meson test timeouts to improve debuggability Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 01/12] qtest: bump min meson timeout to 60 seconds Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 02/12] qtest: bump migration-test timeout to 5 minutes Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 03/12] qtest: bump qom-test timeout to 15 minutes Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 04/12] qtest: bump npcm7xx_pwn-test timeout to 5 minutes Daniel P. Berrangé
2023-07-19 13:06 ` Thomas Huth
2023-07-19 13:38 ` Peter Maydell
2023-07-17 18:28 ` [PATCH v2 05/12] qtest: bump test-hmp timeout to 4 minutes Daniel P. Berrangé
2023-07-19 13:07 ` Thomas Huth
2023-07-17 18:28 ` [PATCH v2 06/12] qtest: bump pxe-test timeout to 3 minutes Daniel P. Berrangé
2023-07-19 13:08 ` Thomas Huth [this message]
2023-07-19 13:26 ` Thomas Huth
2023-09-12 15:40 ` Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 07/12] qtest: bump prom-env-test " Daniel P. Berrangé
2023-07-19 13:22 ` Thomas Huth
2023-07-19 13:37 ` Thomas Huth
2023-07-19 13:38 ` Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 08/12] qtest: bump boot-serial-test " Daniel P. Berrangé
2023-07-19 13:24 ` Thomas Huth
2023-07-17 18:28 ` [PATCH v2 09/12] qtest: bump qos-test timeout to 2 minutes Daniel P. Berrangé
2023-07-19 13:28 ` Thomas Huth
2023-07-17 18:28 ` [PATCH v2 10/12] qtest: bump aspeed_smc-test timeout to 4 minutes Daniel P. Berrangé
2023-07-19 13:35 ` Thomas Huth
2023-07-17 18:28 ` [PATCH v2 11/12] qtest: bump bios-table-test timeout to 9 minutes Daniel P. Berrangé
2023-07-17 18:28 ` [PATCH v2 12/12] mtest2make: stop disabling meson test timeouts Daniel P. Berrangé
2023-07-18 6:29 ` Philippe Mathieu-Daudé
2023-08-08 8:57 ` [PATCH v2 00/12] tests: enable meson test timeouts to improve debuggability Alex Bennée
2023-08-13 7:02 ` Thomas Huth
2023-08-17 10:36 ` Daniel P. Berrangé
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=b73807c7-ba19-9a22-ddf9-93b0fb2980a3@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=lvivier@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).