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

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

[Pratik Farkase]

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"
 
-- 
2.43.0

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

[patchtest]

[-- Attachment #1: Type: text/plain, Size: 3289 bytes --]

Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch /home/patchtest/share/mboxes/v1-core-image-ptest-raise-ptest-timeout-for-openssl.patch

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)

PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test auh changelog truncation notice (test_mbox.TestMbox.test_auh_changelog_truncation_notice)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test bugzilla entry format (test_mbox.TestMbox.test_bugzilla_entry_format)
PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence)
PASS: test commit message user tags (test_mbox.TestMbox.test_commit_message_user_tags)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)

SKIP: pretest pylint: Python-unidiff parse error (test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: Patch cannot be merged (test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test CVE check ignore: No modified recipes or older target branch, skipping test (test_metadata.TestMetadata.test_cve_check_ignore)
SKIP: test CVE tag format: Parse error Hunk is longer than expected (test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: Parse error Hunk is longer than expected (test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: Parse error Hunk is longer than expected (test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: Python-unidiff parse error (test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: Patch cannot be merged (test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!

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

[Yoann Congal]

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