https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/609/steps/13/logs/stdio Failed ptests: {'python3': ['test_interrupt', 'python3']} qemux86-64-musl-ptest debian13-vk-1 --- FAIL: test_interrupt (test.test_multiprocessing_fork.test_processes.WithProcessesTestProcess.test_interrupt) (...) Warning -- Dangling processes: {<Process name='Process-140' pid=7313 parent=4810 started daemon>} (...) Warning -- Dangling processes: {<Process name='Process-140' pid=7313 parent=4810 started daemon>} ====================================================================== ERROR: test_interrupt (test.test_multiprocessing_fork.test_processes.WithProcessesTestProcess.test_interrupt) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.14/test/_test_multiprocessing.py", line 640, in test_interrupt exitcode = self._kill_process(multiprocessing.Process.interrupt) File "/usr/lib/python3.14/test/_test_multiprocessing.py", line 622, in _kill_process self.assertEqual(join(), None) ~~~~^^ File "/usr/lib/python3.14/test/_test_multiprocessing.py", line 302, in __call__ return self.func(*args, **kwds) ~~~~~~~~~^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/multiprocessing/process.py", line 156, in join res = self._popen.wait(timeout) File "/usr/lib/python3.14/multiprocessing/popen_fork.py", line 44, in wait return self.poll(os.WNOHANG if timeout == 0.0 else 0) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/multiprocessing/popen_fork.py", line 28, in poll pid, sts = os.waitpid(self.pid, flag) ~~~~~~~~~~^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/test/_test_multiprocessing.py", line 618, in handler raise RuntimeError('join took too long: %s' % p) RuntimeError: join took too long: <Process name='Process-140' pid=7313 parent=4810 started daemon> --- Full logs at: https://valkyrie.yocto.io/pub/non-release/20260625-73/testresults/qemux86-64-musl-ptest/python3.log I'm opening a bug for this one so we can track how often it happens and have a better idea on whether we should disable it or not.
qemux86-64-musl-ptest alma8-vk-2 master&master-next completed at 2026-07-07 12:50:21+00:00 https://valkyrie.yocto.io/pub/non-release/20260707-70/testresults/qemux86-64-musl-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/675/steps/14/logs/stdio
qemux86-64-musl-ptest fedora43-vk-2 mathieu/master-next completed at 2026-08-15 07:49:02+00:00 https://valkyrie.yocto.io/pub/non-release/20260815-47/testresults/qemux86-64-musl-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/957/steps/15/logs/stdio
Patch merged: https://git.openembedded.org/openembedded-core/commit/?id=7a7fbf9028bb1f84a3638d06fb1f56f44f258c48
qemux86-64-musl-ptest ubuntu2404-vk-1 wrynose completed at 2026-09-17 17:35:50+00:00 https://autobuilder.yoctoproject.org/valkyrie/?#/builders/110/builds/1210 I need to backport on wrynose: "python3: ptest: skip flaky test_interrupt on musl" https://git.openembedded.org/openembedded-core/commit/?id=7a7fbf9028bb1f84a3638d06fb1f56f44f258c48