From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: berrange@redhat.com
Subject: Re: [PATCH] meson: adjust timeouts for some slower tests
Date: Tue, 9 Feb 2021 09:54:26 -0800 [thread overview]
Message-ID: <9825c4c6-ae01-57ee-6616-86eba1d3b04d@linaro.org> (raw)
In-Reply-To: <20210209174541.150011-1-pbonzini@redhat.com>
On 2/9/21 9:45 AM, Paolo Bonzini wrote:
> Adjust the timeouts for the longest running tests. These are the
> times that I measured and the corresponding timeouts. For generic
> qtests, the target that reported the longest runtime is included.
>
> unit tests:
> test-crypto-tlscredsx509 13.15s 60s
> test-crypto-tlssession 14.12s 60s
>
> qtests:
> ide-test 13.65s 60s
> npcm7xx_watchdog_timer-test 15.02s 60s
> qos-test 21.26s 60s (i386)
> ahci-test 22.18s 60s
> pxe-test 26.51s 90s
> boot-serial-test 28.02s 90s (sparc)
> prom-env-test 28.86s 90s
> bios-tables-test 50.17s 90s (aarch64)
> test-hmp 57.15s 90s (aarch64)
> npcm7xx_pwm-test 71.27s 120s
> migration-test 97.09s 150s (aarch64)
> qom-test 139.20s 180s (aarch64)
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/meson.build | 6 ++++++
> tests/qtest/meson.build | 15 +++++++++++++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/tests/meson.build b/tests/meson.build
> index 0c939f89f7..fde21b6c8f 100644
> --- a/tests/meson.build
> +++ b/tests/meson.build
> @@ -237,6 +237,11 @@ test_env = environment()
> test_env.set('G_TEST_SRCDIR', meson.current_source_dir())
> test_env.set('G_TEST_BUILDDIR', meson.current_build_dir())
>
> +slow_tests = {
> + 'test-crypto-tlscredsx509': 2,
> + 'test-crypto-tlssession': 2
> +}
> +
> foreach test_name, extra: tests
> src = [test_name + '.c']
> deps = [qemuutil]
> @@ -254,6 +259,7 @@ foreach test_name, extra: tests
> env: test_env,
> args: ['--tap', '-k'],
> protocol: 'tap',
> + timeout: 30 * slow_tests.get(test_name, 1),
> suite: ['unit'])
> endforeach
>
> diff --git a/tests/qtest/meson.build b/tests/qtest/meson.build
> index 7e082be6fb..b1f8790b75 100644
> --- a/tests/qtest/meson.build
> +++ b/tests/qtest/meson.build
> @@ -4,6 +4,20 @@ if not config_host.has_key('CONFIG_POSIX')
> subdir_done()
> endif
>
> +slow_qtests = {
> + 'ahci-test' : 2,
> + 'bios-tables-test' : 3,
> + 'boot-serial-test' : 3,
> + 'ide-test' : 2,
> + 'migration-test' : 5,
> + 'npcm7xx_pwm-test': 4,
> + 'npcm7xx_watchdog_timer-test': 2,
> + 'prom-env-test' : 3,
> + 'pxe-test' : 3,
> + 'qos-test : 2,
> + 'qom-test' : 6,
> + 'test-hmp' : 3,
> +]
Mismatched brace?
> qtests_generic = [
> 'cdrom-test',
> 'device-introspect-test',
> @@ -272,6 +286,7 @@ foreach dir : target_dirs
> env: qtest_env,
> args: ['--tap', '-k'],
> protocol: 'tap',
> + timeout: 30 * slow_qtests.get(test_name, 1),
Why scale here, rather than putting the real time in the dict? Is there some
other scaling going on that I can't see?
r~
> suite: ['qtest', 'qtest-' + target_base])
> endforeach
> endforeach
>
next prev parent reply other threads:[~2021-02-09 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 17:45 [PATCH] meson: adjust timeouts for some slower tests Paolo Bonzini
2021-02-09 17:54 ` Richard Henderson [this message]
2021-02-09 18:45 ` Paolo Bonzini
2021-02-09 17:58 ` Daniel P. Berrangé
2021-02-11 11:30 ` Paolo Bonzini
2021-02-11 12:52 ` 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=9825c4c6-ae01-57ee-6616-86eba1d3b04d@linaro.org \
--to=richard.henderson@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).