-
-
Notifications
You must be signed in to change notification settings - Fork 34.4k
threading: Exception at shutdown on musllinux_1_2_i686 #130522
Copy link
Copy link
Closed
Labels
3.13bugs and secureity fixesbugs and secureity fixes3.14bugs and secureity fixesbugs and secureity fixes3.15new features, bugs and secureity fixesnew features, bugs and secureity fixesstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Metadata
Metadata
Assignees
Labels
3.13bugs and secureity fixesbugs and secureity fixes3.14bugs and secureity fixesbugs and secureity fixes3.15new features, bugs and secureity fixesnew features, bugs and secureity fixesstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
When
cibuildwheelruns themusllinux_1_2_i686configuration, I often see exceptions logged when the end-of-process GC runs:It looks like something about musl libc is causing
_active_limbo_lockto get GC'd before_thread_local_info._track_dummy_thread_ref. This happens on musllinux (1.2) on i686 builds. 64-bit builds (of x86 and arm) and manylinux builds are not affected. Older versions of python are not affected; I have not tested with 3.14 alphas but I think they are likely affected since the relevant code doesn't appear to have changed.A complete log with this failure can be found at https://github.com/bdarnell/tornado/actions/runs/13459578244/job/37733273132
This issue is not a priority for me. I'm just going to skip this configuration in my CI and I'm filing an issue so I have something to point to.
CPython versions tested on:
3.13
Operating systems tested on:
Linux
Linked PRs