| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ng build The assignment to `pto->vectorcall` isn't thread-safe in the free threading build. Note that this is already fixed in the main branch.
|
Thanks @colesbury for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
…threading build (pythonGH-143882) pythongh-143880: Fix data race in `functools.partial` in free threading build The assignment to `pto->vectorcall` isn't thread-safe in the free threading build. Note that this is already fixed in the main branch. (cherry picked from commit 0042384) Co-authored-by: Sam Gross <colesbury@gmail.com>
|
GH-145435 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
Saw this trigger a test failure in 3.13 TSan, so might as well backport it to 3.13 |
Sorry, something went wrong.
race:partial_vectorcall_fallback (python/cpython#128050): the race was fixed on the 3.14 branch on 2026-01-16 (python/cpython#143882, follow-up issue python/cpython#143880), so the suppression is most likely dead. It is retained regardless: the hermetic TSAN CPython tarball the workflow downloads is an unversioned "3.14.x" artefact (declared to Bazel as 3.14.3), so nothing pins which source revision it was built from, and a wrongly removed suppression halts the nightly TSAN suite (halt_on_error=1) while a stale one costs nothing. The annotation records the two conditions under which it can go: provenance pinned to a post-fix revision, or a deliberately triggered green TSAN run without it. race:func_set_name (python/cpython#154821): fixed on the 3.14 branch on 2026-07-29 (python/cpython#154831); same removal condition once a rebuilt tarball contains the fix.
| Back | FazBrowse Home | New Git URL |
The assignment to pto->vectorcall isn't thread-safe in the free threading build. Note that this is already fixed in the main branch.