From: Thomas Huth <thuth@redhat.com>
To: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org
Cc: Radoslaw Biernacki <rad@semihalf.com>,
qemu-arm@nongnu.org, Leif Lindholm <quic_llindhol@quicinc.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v2] tests/functional: Convert Aarch64 SBSA-Ref avocado tests
Date: Thu, 22 Aug 2024 16:37:55 +0200 [thread overview]
Message-ID: <33638ae6-9e3e-4ad4-85ff-abf448d50d22@redhat.com> (raw)
In-Reply-To: <d8c744cf-0da1-42fc-92cc-f8bec8ca00e1@linaro.org>
On 22/08/2024 16.06, Marcin Juszkiewicz wrote:
> On 22.08.2024 13:41, Philippe Mathieu-Daudé wrote:
>> # Timeouts for individual tests that can be slow e.g. with debugging
>> enabled
>> test_timeouts = {
>> + 'aarch64_sbsaref' : 180,
>
> What kind of machine is able to run those tests in 180s? I bumped them to
> 2400s and got timeout (Macbook with M1 Pro).
>
> "make check-avocado" (with some AVOCADO_* vars to limit list of tests) shown
> me which test is run and pass/fail for each.
>
> "make check-functional-aarch64 V=1" shows me "1/4
> qemu:func-thorough+func-aarch64-thorough+thorough /
> func-aarch64-aarch64_sbsaref" and timeouts without information which tests
> pass, which fail.
Try running "make check-functional V=1" ... it should show you the
individual subtests, so you hopefully can conclude from the tests that
succeeded to the one that was hanging.
Thomas
next prev parent reply other threads:[~2024-08-22 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 11:41 [PATCH v2] tests/functional: Convert Aarch64 SBSA-Ref avocado tests Philippe Mathieu-Daudé
2024-08-22 12:34 ` Thomas Huth
2024-08-22 14:06 ` Marcin Juszkiewicz
2024-08-22 14:37 ` Thomas Huth [this message]
2024-08-22 14:39 ` Philippe Mathieu-Daudé
2024-08-22 14:43 ` Thomas Huth
2024-08-22 18:57 ` Marcin Juszkiewicz
2024-08-23 13:12 ` Philippe Mathieu-Daudé
2024-08-22 18:48 ` Marcin Juszkiewicz
2024-08-23 6:20 ` Philippe Mathieu-Daudé
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=33638ae6-9e3e-4ad4-85ff-abf448d50d22@redhat.com \
--to=thuth@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.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).