Skip to content

bpo-37244: Increase robustness of test_resource_tracker #14288

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

Merged

Conversation

pierreglaser
Copy link
Contributor

@pierreglaser pierreglaser commented Jun 21, 2019

Attempt to fix the buildbot failures reported in the original bpo issue.
From the failure tracebacks, I suspect it is only because the cleanup time given to the resource_tracker was not high enough (2 seconds). I increased it to to 60 seconds.

cc @vstinner :)

https://bugs.python.org/issue37244

@miss-islington
Copy link
Contributor

Thanks @pierreglaser for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jun 25, 2019
…-14288)

Increase robustness of test_resource_tracker(): retry for 60 seconds.
(cherry picked from commit e1a63c4)

Co-authored-by: Pierre Glaser <[email protected]>
@bedevere-bot
Copy link

GH-14383 is a backport of this pull request to the 3.8 branch.

miss-islington added a commit that referenced this pull request Jun 25, 2019
Increase robustness of test_resource_tracker(): retry for 60 seconds.
(cherry picked from commit e1a63c4)

Co-authored-by: Pierre Glaser <[email protected]>
lisroach pushed a commit to lisroach/cpython that referenced this pull request Sep 10, 2019
…-14288)

Increase robustness of test_resource_tracker(): retry for 60 seconds.
DinoV pushed a commit to DinoV/cpython that referenced this pull request Jan 14, 2020
…-14288)

Increase robustness of test_resource_tracker(): retry for 60 seconds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants