Bug 16318

Summary: AB-INT PTEST: python3 ptest failure: in test_tracemalloc
Product: [QA/Testing] Package Testing (ptest) Reporter: João Marcos Costa <joaomarcos.costa>
Component: ptestAssignee: Unassigned <unassigned>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: mathieu.dubois-briand, randy.macleod, richard.purdie
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description João Marcos Costa 2026-06-15 11:12:20 UTC 
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/493/steps/13/logs/stdio

qemuarm64-musl-ptest stream10-vk-arm1


https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/510/steps/13/logs/stdio

qemuarm64-musl-ptest ubuntu2404-vk-arm2

The stdio shows only this:

Failed ptests:
{'python3': ['python3']}

and the logs are more specific:

"""
0:04:29 load avg: 2.68 [413/486/1] test_tracemalloc worker non-zero exit code (Exit code -11 (SIGSEGV)) -- running (1): test_socket (40.6 sec)
PASS: test_late_untrack (test.test_tracemalloc.TestCAPI.test_late_untrack)
PASS: test_stop_track (test.test_tracemalloc.TestCAPI.test_stop_track)
PASS: test_stop_untrack (test.test_tracemalloc.TestCAPI.test_stop_untrack)
test_tracemalloc_track_race (test.test_tracemalloc.TestCAPI.test_tracemalloc_track_race) ... Fatal Python error: Segmentation fault

Thread 0x0000ffff86e25af8 [python3] (most recent call first):
  <no Python frame>

(...)

Thread 0x0000ffff8cecdaf8 [python3] (most recent call first):
  <no Python frame>

Thread 0x0000ffff8f0fed28 [python3] (most recent call first):
  File "/usr/lib/python3.14/test/test_tracemalloc.py", line 1120 in test_tracemalloc_track_race
  File "/usr/lib/python3.14/unittest/case.py", line 615 in _callTestMethod
  File "/usr/lib/python3.14/unittest/case.py", line 669 in run
  File "/usr/lib/python3.14/unittest/case.py", line 725 in __call__
  File "/usr/lib/python3.14/unittest/suite.py", line 122 in run
  File "/usr/lib/python3.14/unittest/suite.py", line 84 in __call__
  File "/usr/lib/python3.14/unittest/suite.py", line 122 in run
  File "/usr/lib/python3.14/unittest/suite.py", line 84 in __call__
  File "/usr/lib/python3.14/unittest/runner.py", line 257 in run
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 84 in _run_suite
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 42 in run_unittest
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 162 in test_func
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 118 in regrtest_runner
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 165 in _load_run_test
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 210 in _runtest_env_changed_exc
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 319 in _runtest
  File "/usr/lib/python3.14/test/libregrtest/single.py", line 348 in run_single_test
  File "/usr/lib/python3.14/test/libregrtest/worker.py", line 99 in worker_process
  File "/usr/lib/python3.14/test/libregrtest/worker.py", line 137 in main
  File "/usr/lib/python3.14/test/libregrtest/worker.py", line 141 in <module>
  File "<frozen runpy>", line 88 in _run_code
  File "<frozen runpy>", line 203 in _run_module_as_main

Current thread's C stack trace (most recent call first):
  <cannot get C stack on this system>
"""

Full logs at: https://valkyrie.yocto.io/pub/non-release/20260605-123/testresults/qemuarm64-musl-ptest/python3.log
Comment 2 Randy MacLeod 2026-06-18 14:41:17 UTC 
It's a duplicate

*** This bug has been marked as a duplicate of bug 16182 ***