bpo-30387: Fix warning in test_threading by vstinner · Pull Request #1634 · python/cpython (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation1 Commits1 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
test_is_alive_after_fork() now joins directly the thread to avoid the
following warning added by bpo-30357:
Warning -- threading_cleanup() failed to cleanup 0 threads
after 2 sec (count: 0, dangling: 21)
Use also a different exit code to catch generic exit code 1.
test_is_alive_after_fork() now joins directly the thread to avoid the following warning added by bpo-30357:
Warning -- threading_cleanup() failed to cleanup 0 threads after 2 sec (count: 0, dangling: 21)
Use also a different exit code to catch generic exit code 1.
vstinner added a commit that referenced this pull request
test_is_alive_after_fork() now joins directly the thread to avoid the following warning added by bpo-30357:
Warning -- threading_cleanup() failed to cleanup 0 threads after 2 sec (count: 0, dangling: 21)
Use also a different exit code to catch generic exit code 1. (cherry picked from commit f8d05b3)
vstinner added a commit that referenced this pull request
test_is_alive_after_fork() now joins directly the thread to avoid the following warning added by bpo-30357:
Warning -- threading_cleanup() failed to cleanup 0 threads after 2 sec (count: 0, dangling: 21)
Use also a different exit code to catch generic exit code 1. (cherry picked from commit f8d05b3)