Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Pratik Farkase <pratik.farkase@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com, Pratik Farkase <pratik.farkase@est.tech>
Subject: [OE-core][PATCH v1] core-image-ptest: raise ptest timeout for openssl
Date: Fri, 18 Sep 2026 12:29:21 +0200	[thread overview]
Message-ID: <20260918102921.20511-1-pratik.farkase@est.tech> (raw)

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



             reply	other threads:[~2026-09-18 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 10:29 Pratik Farkase [this message]
2026-09-18 11:01 ` Patchtest results for [OE-core][PATCH v1] core-image-ptest: raise ptest timeout for openssl patchtest
2026-09-18 12:35 ` Yoann Congal

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=20260918102921.20511-1-pratik.farkase@est.tech \
    --to=pratik.farkase@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pratik.farkase@ericsson.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