bpo-37244: Increase robustness of test_resource_tracker#14288
Merged
vstinner merged 2 commits intoJun 25, 2019
Conversation
vstinner
reviewed
Jun 21, 2019
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
|
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
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.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_trackerwas not high enough (2 seconds). I increased it to to 60 seconds.cc @vstinner :)
https://bugs.python.org/issue37244