https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3292/steps/13/logs/stdio Failed ptests: {'tcl': ['tests/mutex.test']} qemuarm64-ptest debian13-vk-arm1 --- Only running test files that match: mutex.test Tests began at 2026-03-18 18:48:10 +0000 mutex.test ==== mutex-condition-5 mutex condition 4/5/40000/0 FAILED ==== Contents of test case: lassign [testmutex condition $nthreads $recursion $iters $yield] enqTotal enqPerThread enqTimeouts deqTotal deqPerThread deqTimeouts list $enqTotal [fairness $totalOps $enqPerThread] $enqTimeouts $deqTotal [fairness $totalOps $deqPerThread] $deqTimeouts ---- Result was: 160000 {} 0 160000 {Thread share 17206 < 0.25 fair share 80000} 0 ---- Result should have been (exact matching): 160000 {} 0 160000 {} 0 ==== mutex-condition-5 FAILED Tests ended at 2026-03-18 18:48:17 +0000 all.tcl: Total 12 Passed 11 Skipped 0 Failed 1 Sourced 1 Test Files. Files with failing tests: mutex.test FAIL: tests/mutex.test --- Full logs available at: https://valkyrie.yocto.io/pub/non-release/20260318-109/testresults/qemuarm64-ptest/tcl.log
Likely just skip this test.
mutex.test is entirely about load balancing which feels fragile on a loaded system, we can skip it.
Patch on the list.
Fixed in 6c7280df18dae692e23d0e26a0fb4d2fd68bd51d.