-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-117657: Replace TSAN suppresions with more specific rules #118722
Conversation
It looks like the free-threading TSAN tests are failing. |
Tests are passing now but @mpage pointed out that I should probably do some more stress-testing of this before landing, since there are likely more warnings that just show up less frequently. |
I'm seeing a race sometimes reported in https://gist.github.com/colesbury/c0a6edcdf7e909191490cedd3873a062 EDIT: there are a few variations of this, and I think something like |
Another race between |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks @swtaarrs for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…ythonGH-118722) Using `race:` filters out warnings if the function appears anywhere in the stack trace. This can hide a lot of unrelated warnings, especially for a function like `_PyEval_EvalFrameDefault`, which is somewhere on the stack more often than not. Change all free-threaded suppressions to `race_top:`, which only matches the top frame, and add any new suppressions this exposes. (cherry picked from commit 98ff3f6) Co-authored-by: Brett Simmers <[email protected]>
GH-118870 is a backport of this pull request to the 3.13 branch. |
…H-118722) (#118870) Using `race:` filters out warnings if the function appears anywhere in the stack trace. This can hide a lot of unrelated warnings, especially for a function like `_PyEval_EvalFrameDefault`, which is somewhere on the stack more often than not. Change all free-threaded suppressions to `race_top:`, which only matches the top frame, and add any new suppressions this exposes. (cherry picked from commit 98ff3f6) Co-authored-by: Brett Simmers <[email protected]>
|
The buildbot failure looks unrelated |
|
…ython#118722) Using `race:` filters out warnings if the function appears anywhere in the stack trace. This can hide a lot of unrelated warnings, especially for a function like `_PyEval_EvalFrameDefault`, which is somewhere on the stack more often than not. Change all free-threaded suppressions to `race_top:`, which only matches the top frame, and add any new suppressions this exposes.
Using
race:
filters out warnings if the function appears anywhere in the stack trace. This can hide a lot of unrelated warnings, especially for a function like_PyEval_EvalFrameDefault
, which is somewhere on the stack more often than not.Change all free-threaded suppressions to
race_top:
, which only matches the top frame, and add any new suppressions this exposes. I iterated the test suite under TSAN until it could go 5 times in a row without any new warnings.