Re: [OE-core][PATCH v1] core-image-ptest: raise ptest timeout for openssl

["Yoann Congal" <yoann.congal@smile.fr>]

On Fri Sep 18, 2026 at 12:29 PM CEST, Pratik Farkase via lists.openembedded.org wrote:
> The openssl ptest suite passes but its total runtime can exceed the
> default 450s ptest-runner timeout on loaded autobuilder workers
> (observed DURATION 566s on qemux86-64-musl), so ptest-runner kills the
> run with "Timeout!" and it is reported as a failure even though no
> individual test failed.
>
> [YOCTO #16430]
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
>  meta/recipes-core/images/core-image-ptest.bb | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-core/images/core-image-ptest.bb b/meta/recipes-core/images/core-image-ptest.bb
> index 22bb23c0e7..f61399abe5 100644
> --- a/meta/recipes-core/images/core-image-ptest.bb
> +++ b/meta/recipes-core/images/core-image-ptest.bb
> @@ -11,6 +11,10 @@ HOMEPAGE = "https://www.yoctoproject.org/"
>  PTESTS = "${PTESTS_SLOW} ${PTESTS_FAST}"
>  PTEST_RUNNER_TIMEOUT:virtclass-mcextend-python3-cffi = "600"
>  PTEST_RUNNER_TIMEOUT:virtclass-mcextend-go = "4800"
> +PTEST_RUNNER_TIMEOUT:virtclass-mcextend-openssl = "700"
>  
>  IMAGE_INSTALL:append = " ${MCNAME}-ptest openssh"
>  

Hello,

Thanks for looking at my bugs :)

FYI, the patchtest issue:
  FAIL: test mbox format: Series has malformed diff lines.
  Create the series again using git-format-patch and ensure it applies using git am (test_mbox.TestMbox.test_mbox_format)
is caused by "@@ -11,6 +11,10 @@":
                           ^
This means the chunck is expected to be 10 lines long after the patch (I
think 7 should work here but - please - regenerate the patch from git,
it will compute that.

On the patch content itself, we don't usualy increase timeout without a
good reason like high AB-INT frequency, analysis to show that this is
the right solution.

In this case, if you want to look at this bug, I think you should try to
determine what happened. For exemple, which test triggered the timeout?
Is this test prone to load related issues? Is there a related issue
upstream? a fix? ...
If you don't want to look at this, I'm fine with waiting to see if how
opften it reproduces (if ever).

Regards,
-- 
Yoann Congal
Smile ECS