-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
test_pyrepl.run_repl
timeout is too small
#121605
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
Comments
We also need to close the `slave_fd` earlier so that reading from `master_fd` won't block forever when the subprocess finishes.
We also need to close the `slave_fd` earlier so that reading from `master_fd` won't block forever when the subprocess finishes.
We also need to close the `slave_fd` earlier so that reading from `master_fd` won't block forever when the subprocess finishes.
Ugh, bad news is that this seemed to slow down the refleaks buildbots, but not the normal buildbots. I'm not entirely sure why yet and I haven't reproduced the issue locally: Before: https://buildbot.python.org/?#/builders/1226/builds/2221 (total: 18 mins, pyrepl not in slowest tests) |
So I think the issue is that on the buildbots, pyrepl isn't available and one of the tests calls
|
The fallback repl does not support "exit" without parentheses, so the test would hang until the timeout expired.
The fallback repl does not support "exit" without parentheses, so the test would hang until the timeout expired.
…-121820) The fallback repl does not support "exit" without parentheses, so the test would hang until the timeout expired.
Uh oh!
There was an error while loading. Please reload this page.
The timeout in
run_repl
of 0.5 seconds is too small and leads to spurious failures on slow/heavily loaded machines, or when running with sanitizers:cpython/Lib/test/test_pyrepl/test_pyrepl.py
Line 951 in ef10110
(This is my second attempt at describing the problems I ran into with #121603)
Linked PRs
The text was updated successfully, but these errors were encountered: