From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests/tcg/multiarch: Give the 'memory' TCG test a larger timeout
Date: Mon, 04 Mar 2024 18:26:43 +0000 [thread overview]
Message-ID: <87v861x38c.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA9QbbOuzeo+bTRAdTCS2h6gTocbMsgj3k3DNP=H4Bh0Ag@mail.gmail.com> (Peter Maydell's message of "Mon, 4 Mar 2024 17:28:46 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> Ping for review?
Ahh we crossed streams because I merged:
cdb5bfc9f34 (tests/tcg: bump TCG test timeout to 120s)
Do we need even more time?
>
> thanks
> -- PMM
>
> On Tue, 27 Feb 2024 at 14:23, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> The 'memory' TCG test times out intermittently on our cross-i686-tci
>> CI job. We expect this to be a slow config (it's using TCI), so it's
>> possible that when the CI runner is heavily loaded it tips past
>> the timeout.
>>
>> Double the timeout for tests. If this doesn't resolve the
>> intermittents we can assume we're looking at some kind of
>> TCI-specific hang.
>>
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2079
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> I could not figure out a way to get the timeout to apply to the
>> 'memory' test specifically (including all its variants like
>> running with plugins or the gdbserver or record-replay).
>> ---
>> tests/tcg/Makefile.target | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/tcg/Makefile.target b/tests/tcg/Makefile.target
>> index 8cf65f68dd8..af1a18cee1b 100644
>> --- a/tests/tcg/Makefile.target
>> +++ b/tests/tcg/Makefile.target
>> @@ -98,7 +98,8 @@ QEMU_OPTS=
>> # 15s original default
>> # 60s with --enable-debug
>> # 90s with --enable-tcg-interpreter
>> -TIMEOUT=90
>> +# The 'memory' test in particular is very slow under TCI.
>> +TIMEOUT=180
>>
>> ifeq ($(filter %-softmmu, $(TARGET)),)
>> # The order we include is important. We include multiarch first and
>> --
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-03-04 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:23 [PATCH] tests/tcg/multiarch: Give the 'memory' TCG test a larger timeout Peter Maydell
2024-03-04 17:28 ` Peter Maydell
2024-03-04 18:26 ` Alex Bennée [this message]
2024-03-04 20:44 ` 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=87v861x38c.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--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).