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] openssl: ptest: skip test_quic_multistream due to intermittent timeout
Date: Wed, 12 Aug 2026 14:08:37 +0200 [thread overview]
Message-ID: <20260812120837.35922-1-pratik.farkase@est.tech> (raw)
The quic_multistream_test has a 60-second internal per-operation deadline
that is too tight under QEMU emulation on loaded autobuilder hosts. The
test creates 200 server-initiated streams in a loop, and if any single
operation exceeds 60s due to scheduling delays, the test fails with a
timeout error.
It is tracked upstream as : https://github.com/openssl/openssl/issues/27104
[YOCTO #15357]
Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
meta/recipes-connectivity/openssl/openssl/run-ptest | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-connectivity/openssl/openssl/run-ptest b/meta/recipes-connectivity/openssl/openssl/run-ptest
index cd29bb1446..aac0c5b55f 100644
--- a/meta/recipes-connectivity/openssl/openssl/run-ptest
+++ b/meta/recipes-connectivity/openssl/openssl/run-ptest
@@ -8,8 +8,11 @@ set -eu
if test $# -gt 0; then
TESTS=$*
else
- # Skip test_symbol_presence as this is for developers
- TESTS="alltests -test_symbol_presence"
+ # Skip test_symbol_presence as this is for developers.
+ # Skip test_quic_multistream as it has a 60s internal timeout per
+ # operation that is too tight under QEMU emulation on loaded hosts,
+ # causing intermittent failures (upstream: https://github.com/openssl/openssl/issues/27104)
+ TESTS="alltests -test_symbol_presence -test_quic_multistream"
fi
export TOP=.
--
2.43.0
reply other threads:[~2026-08-12 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260812120837.35922-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