Repository navigation
Use faster CI coverage library - #2093
Merged
Merged
Conversation
coverage.py uses sys.monitoring by default on 3.14+, far faster than the 3.13 settrace core (3.13 coverage job took ~9 min vs ~3 for others). AI-assisted (Claude)
mscuthbert
changed the title
|
coverage: 93.381% (-0.001%) from 93.382% — coverage-314 into master |
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
2 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.
Coverage got a lot faster in Python 3.14. So I'm moving the coverage check there (even though I usually run it on the second oldest OS system).
Before -- most tests took 3min; 3.13 w/ coverage took 9min.
Now - other tests still take 3min; 3.14 w/ coverage took 3min 40 sec!
AI-assisted (Claude)