From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Leif Lindholm <quic_llindhol@quicinc.com>,
Radoslaw Biernacki <rad@semihalf.com>,
Peter Maydell <peter.maydell@linaro.org>,
Cleber Rosa <crosa@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [PATCH v4 1/2] tests/avocado: sbsa-ref: add FreeBSD tests
Date: Wed, 3 Jul 2024 16:09:48 +0200 [thread overview]
Message-ID: <693bb711-3f45-49e4-89f5-b7ee1b2d215b@linaro.org> (raw)
In-Reply-To: <20240703-b4-move-to-freebsd-v4-1-07191f958530@linaro.org>
On 3/7/24 16:06, Marcin Juszkiewicz wrote:
> FreeBSD has longer support cycle for stable release (14.x EoL in 2028)
> than OpenBSD (7.3 we used is already EoL). Also bugfixes are backported
> so we can stay on 14.x for longer. Tests done on OpenBSD will now be
> done using FreeBSD.
>
> OpenBSD 7.3 stays with Cortex-A57 test for local runs only.
>
> Moved from Neoverse-N1 to Neoverse-N2 as sbsa-ref defaults were changed.
>
> Timeout messages expanded to mention being affected by PAuth emulation.
>
> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
> ---
> tests/avocado/machine_aarch64_sbsaref.py | 73 ++++++++++++++++++++++++--------
> 1 file changed, 55 insertions(+), 18 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-07-03 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:06 [PATCH v4 0/2] tests/avocado: updates for sbsa-ref testing Marcin Juszkiewicz
2024-07-03 14:06 ` [PATCH v4 1/2] tests/avocado: sbsa-ref: add FreeBSD tests Marcin Juszkiewicz
2024-07-03 14:09 ` Philippe Mathieu-Daudé [this message]
2024-07-03 14:06 ` [PATCH v4 2/2] tests/avocado: add test for default sbsa-ref cpu Marcin Juszkiewicz
2024-07-03 14:11 ` 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=693bb711-3f45-49e4-89f5-b7ee1b2d215b@linaro.org \
--to=philmd@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.com \
--cc=wainersm@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).