Fix py37 coverage #970
Merged
Fix py37 coverage #970
Conversation
This file contains 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
bhrutledge
commented
Jan 3, 2023
bhrutledge
force-pushed
the
fix-py37-coverage
branch
from
cf040f8
to
1a8a175
Compare
Sign up for free
to 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.
Addressing this morning's CI failure, described in detail in nedbat/coveragepy#1524.
I also took the opportunity to clean up the coverage output, by recording dynamic context for the HTML report, and not reporting files with 100% coverage. I thought about removing the HTML report, but left it in because it's really useful locally.