From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: jdmason@kudzu.us, Jon Mason <jon.mason@arm.com>,
meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH 6/6] arm/oeqa: increase optee test timeout
Date: Wed, 8 May 2024 11:32:39 +0300 [thread overview]
Message-ID: <Zjs4p5vDd9AhPI0v@nuoska> (raw)
In-Reply-To: <17CD74F8C81EDD3F.8817@lists.yoctoproject.org>
Hi,
On Wed, May 08, 2024 at 11:07:20AM +0300, Mikko Rapeli via lists.yoctoproject.org wrote:
> Hi,
>
> On Tue, May 07, 2024 at 02:21:36PM -0400, Jon Mason via lists.yoctoproject.org wrote:
> > On Tue, May 07, 2024 at 01:33:13PM -0400, Jon Mason wrote:
> > > OPTEE tests are failing in CI on slower systems due to timing out, but
> > > actually finish when given enough time to complete. Increase the
> > > timeout value to be roughly 100 seconds longer than the time it is
> > > currently taking to finish on the slower systems.
> > >
> > > Signed-off-by: Jon Mason <jon.mason@arm.com>
> >
> > This should have:
> > Fixes: d4507866677c ("oeqa runtime: add optee.py test")
>
> Yes, the optee xtest execution time depends heavily on the target machine,
> real or emulated with qemu. Also, the number of tests and thus execution time
> are increasing in every optee release.
>
> Acked-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Maybe worth mentioning that with our Trusted Substrate firmware
https://gitlab.com/Linaro/trustedsubstrate/meta-ts/
which has TPM support and UEFI secure boot configured with tf-a, u-boot etc
for multiple boards, compared to qemuarm64-secureboot and qemuarm-secureboot
in meta-arm, we had some hangs with this test under oeqa and qemu.
Same hangs did not happen on real HW. Something to do with serial port
handling in qemu and how oeqa python framework uses them. Thus we set the timeouts
to be quite close to the real execution time to avoid long delays in detecting the
error situation. Good thing is that optee xtest does allow to skip/filter out tests
which are known to cause problems.
https://gitlab.com/Linaro/trusted-reference-stack/trs/-/blob/main/meta-trs/lib/oeqa/runtime/cases/opteetest.py?ref_type=heads
Cheers,
-Mikko
next prev parent reply other threads:[~2024-05-08 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 17:33 [PATCH 1/6] arm/gn: update to latest commit Jon Mason
2024-05-07 17:33 ` [PATCH 2/6] arm-bsp: remove support for n1sdp Jon Mason
2024-05-07 17:33 ` [PATCH 3/6] arm-bsp: remove unused recipes Jon Mason
2024-05-07 17:33 ` [PATCH 4/6] CI: increase bitbake server timeout Jon Mason
2024-05-07 17:33 ` [PATCH 5/6] arm/optee: update to 4.2.0 Jon Mason
2024-05-07 17:33 ` [PATCH 6/6] arm/oeqa: increase optee test timeout Jon Mason
2024-05-07 18:21 ` Jon Mason
2024-05-08 8:07 ` [meta-arm] " Mikko Rapeli
[not found] ` <17CD74F8C81EDD3F.8817@lists.yoctoproject.org>
2024-05-08 8:32 ` Mikko Rapeli [this message]
2024-05-08 15:16 ` Jon Mason
2024-05-08 15:38 ` [PATCH 1/6] arm/gn: update to latest commit Jon Mason
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=Zjs4p5vDd9AhPI0v@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=jdmason@kudzu.us \
--cc=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).