-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
test_concurrent_futures: test_deadlock failed with timeout on ARM Raspbian 3.x #109702
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
Labels
tests
Tests in the Lib/test dir
Comments
vstinner
added a commit
to vstinner/cpython
that referenced
this issue
Sep 22, 2023
Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures.
vstinner
added a commit
that referenced
this issue
Sep 22, 2023
Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 22, 2023
…GH-109703) Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures. (cherry picked from commit 1eb1b45) Co-authored-by: Victor Stinner <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 22, 2023
…GH-109703) Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures. (cherry picked from commit 1eb1b45) Co-authored-by: Victor Stinner <[email protected]>
csm10495
pushed a commit
to csm10495/cpython
that referenced
this issue
Sep 28, 2023
…#109703) Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures.
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this issue
Sep 2, 2024
…#109703) Replace SHORT_TIMEOUT with LONG_TIMEOUT in test_deadlock of test_concurrent_futures.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Example:
build: https://buildbot.python.org/all/#/builders/424/builds/4978
These tests passed when re-run in verbose mode in a fresh process.
It's just a timeout issue because the machine was too busy.
Full logs:
Linked PRs
The text was updated successfully, but these errors were encountered: