-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
GH-110796: fix intermittent test failure in test_current_exceptions #110797
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
Conversation
…ions Signed-off-by: Filipe Laíns <[email protected]>
@jd, I know it has been a while, but as the original author, could you have a look? Did I missing something, or is my interpretation sane? Thanks! |
if leave_g.wait(timeout=support.LONG_TIMEOUT): | ||
break | ||
|
||
t = threading.Thread(target=f123) | ||
t.start() | ||
entered_g.wait() | ||
g_raised.wait(timeout=support.LONG_TIMEOUT) |
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.
Also added a timeout here, as if an unexpected exception is raised in the thread, the event will never be set, and we will deadlock.
The Windows failure is GH-110800. |
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.
This looks like a good fix, you need to change the comment on L536 though 😄
Signed-off-by: Filipe Laíns <[email protected]>
Thanks! I forgot that. |
test_sys.SysModuleTest.test_current_exceptions
#110796