-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-132912: Account for race in test_keyboard_interrupt in test_remote_pdb #132929
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
pablogsal
commented
Apr 25, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: test_remote_pdb hangs randomly #132912
There was a very rare race here as the test can be interrupted just when we are leaving the socket synchronization function before we go back to the main function |
Tested locally as @vstinner did and couldn't find anything for 2000 iterations:
|
CC @godlygeek |
Somehow related: test_remote_pdb can still fail on a heavy loaded machine because of its hardcoded timeout of 5 seconds. I wrote #132939 to fix this issue. |
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 cannot make it fail, it looks way more reliable.
I tested on a Linux laptop with 12 logical CPUs:
- 4 terminals running:
./python -m test test_remote_pdb -m test_keyboard_interrupt -v --timeout=15 --forever
- 1 terminal running:
./python -m test test_remote_pdb -m test_keyboard_interrupt -W --timeout=60 --forever -j150
I ran my test for 5 minutes. The system load was around 162.
Fantastic. Thanks for the help @vstinner! |