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] procps: ptest: skip kill test due to race condition
Date: Mon, 17 Aug 2026 09:53:27 +0200 [thread overview]
Message-ID: <20260817075327.8764-1-pratik.farkase@est.tech> (raw)
The kill dejagnu test has a race condition where the test_process helper
can exit or become unavailable before the expect script reads its output,
resulting in 'spawn id not open' errors. This causes intermittent
'kill with SIGUSR1' failures on the autobuilder, particularly on
qemuarm64.
This is tracked upstream at https://gitlab.com/procps-ng/procps/-/issues/423
[YOCTO #16263]
Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
meta/recipes-extended/procps/procps/run-ptest | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/meta/recipes-extended/procps/procps/run-ptest b/meta/recipes-extended/procps/procps/run-ptest
index 7e132653b0..40dbd35265 100644
--- a/meta/recipes-extended/procps/procps/run-ptest
+++ b/meta/recipes-extended/procps/procps/run-ptest
@@ -3,6 +3,13 @@
# Run testsuite which use dejagnu
cd ./testsuite
for tool in @DEJATOOL@; do
+ # Skip the kill test as it has a race condition where test_process
+ # can exit before the expect script reads from it, causing
+ # "spawn id not open" errors (upstream: https://gitlab.com/procps-ng/procps/-/issues/423)
+ if [ "$tool" = "kill" ]; then
+ echo "SKIP: kill (flaky, upstream issue #423)"
+ continue
+ fi
runtest -a --tool $tool --outdir ../log
done
cd -
--
2.43.0
next reply other threads:[~2026-08-17 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 7:53 Pratik Farkase [this message]
2026-08-17 8:28 ` [OE-core][PATCH v2] procps: ptest: skip signal-based kill tests due to race condition Pratik Farkase
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=20260817075327.8764-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