You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 929f628
Browse filesBrowse the repository at this point in the historyBrowse files
pystack: deselect riscv64 native-frame tests broken on target 3.13+
CI (run 36351368476) had 28 identical test failures on Python 3.13,
3.14 and 3.14t while 3.12 passed clean. All 28 assert that pystack can
classify a native frame from a *target* process's own unwind as the
CPython eval loop or GC collector; on riscv64 that classification never
succeeds once the target interpreter is 3.13+, matching gotcha 33/169's
"identical failures on newer interpreters, clean on older" shape one
level removed (it's the target being inspected, not the one running
pytest). pystack itself only ships a signal-frame unwind fix for
AArch64 (elfutils-aarch64-signal-frame.patch, bloomberg/pystack
#341/#348) with no riscv64 equivalent, so this is a documented
per-arch native-unwind gap, not a defect in the wheel under test.
Deselect only the affected tests, generated once per matrix entry from
matrix.python_version so 3.12 keeps running the full suite unchanged.
See gotcha 597 (skills/python-project-porting).
0 commit comments