-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
test_concurrent_futures
TSAN failures
#130605
Comments
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Feb 26, 2025
…CI job There are a number of data races in the default build without suppressions that are exposed by this test. Disable the test for now under TSAN until we have suppressions or fix the data races.
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Feb 26, 2025
The interval may be concurrently read by a thread attempting to acquire the GIL.
colesbury
added a commit
that referenced
this issue
Feb 26, 2025
…gh-130606) There are a number of data races in the default build without suppressions that are exposed by this test. Disable the test for now under TSAN until we have suppressions or fix the data races.
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Feb 27, 2025
The interval may be concurrently read by a thread attempting to acquire the GIL.
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Feb 27, 2025
The interval may be concurrently read by a thread attempting to acquire the GIL.
I think these are fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
I enabled
test_concurrent_futures
in the thread sanitizer job yesterday in:Unfortunately, this is causing fairly frequent failures in the TSAN job, especially for the default (GIL-enabled) build, which I hadn't tested sufficiently with TSAN.
I'll temporarily remove
test_concurrent_futures
while I work on fixing the races.Races
take_gil
and_PyEval_SetSwitchInterval
Linked PRs
The text was updated successfully, but these errors were encountered: