-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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-131677: Fix flaky test_lru_cache_threaded3 #131679
gh-131677: Fix flaky test_lru_cache_threaded3 #131679
Conversation
The call to `with self.subTest(...)` was not thread-safe.
@serhiy-storchaka This is your code. Do you want to take a look? @colesbury Can |
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
I think practically you'd have to get rid of |
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! 👍
Surprised that it did not fail more often. 🤔
As you fix these, perhaps keep a list of tools that are intrinsically single-threaded. Such as list might be useful for linters and it might make a good FAQ entry. |
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
The call to `with self.subTest(...)` was not thread-safe. (cherry picked from commit a123245) Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-131692 is a backport of this pull request to the 3.13 branch. |
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
The call to `with self.subTest(...)` was not thread-safe. (cherry picked from commit a123245) Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-131693 is a backport of this pull request to the 3.12 branch. |
The call to
with self.subTest(...)
was not thread-safe.test_lru_cache_threaded3
#131677