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] python3: ptest: skip flaky test_interrupt on musl
Date: Thu, 20 Aug 2026 15:21:54 +0200 [thread overview]
Message-ID: <20260820132154.29658-1-pratik.farkase@est.tech> (raw)
The test_interrupt test in test_multiprocessing_fork intermittently fails
on musl-based systems under load. The test sends an interrupt signal to a
child process and expects it to join within a timeout, but on loaded
autobuilder hosts the join times out with 'join took too long'.
This has been observed consistently on qemux86-64-musl-ptest across
multiple autobuilder runs. The same test class is tracked upstream at
https://github.com/python/cpython/issues/133651 and is part of the
broader timing-sensitive tests issue at
https://github.com/python/cpython/issues/130363
[YOCTO #16348]
Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
---
meta/recipes-devtools/python/python3_3.14.7.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/python/python3_3.14.7.bb b/meta/recipes-devtools/python/python3_3.14.7.bb
index 53a9ca59b5..568e632278 100644
--- a/meta/recipes-devtools/python/python3_3.14.7.bb
+++ b/meta/recipes-devtools/python/python3_3.14.7.bb
@@ -335,6 +335,7 @@ SKIPPED_TESTS:append:libc-musl = " \
-x test_threading \
--ignore test.test_strptime.StrptimeTests.test_date_locale2 \
--ignore test.test_ctypes.test_dlerror.TestNullDlsym.test_null_dlsym \
+ --ignore test.test_multiprocessing_fork.test_processes.WithProcessesTestProcess.test_interrupt \
"
--
2.43.0
reply other threads:[~2026-08-20 13:22 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=20260820132154.29658-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.