Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
CI: ban coverage 6.3 that may be causing random hangs in fork test#22326
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
jklymak approved these changesJan 26, 2022
QuLogic approved these changesJan 26, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Not entirely sure why this broke things, but I see the change in dependencies in the Actions logs, as you say.
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull requestJan 26, 2022
…g random hangs in fork test
Might be an upstream issue here:nedbat/coveragepy#1310 |
tacaswell added a commit that referenced this pull requestJan 26, 2022
…326-on-v3.5.xBackport PR#22326 on branch v3.5.x (CI: ban coverage 6.3 that may be causing random hangs in fork test)
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
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.
PR Summary
About 24 hours ago (some time 2022-01-25) we started getting random failures on CI that look like:
We are seeing this mostly on py37, but it also showed up on 3.8 / 3.9 so this won't just go away when we merge#22194 .
The only version change between the last working run to the first failing run was coverage 6.2 -> 6.3. To get coverage on subprocesses there is some extra configuration done at (sub-)process spawn time to get the hooks in place (which is actually managed for us by pytest-cov) so it is plausible that this is related, but do not actually understand the underlying problem.