👷 Speed up the CI by shuffling the test matrix - #1815
Merged
Conversation
svlandeg
changed the title
Contributor
📝 Docs previewLast commit f739c56 at: https://d6f4d26d.typertiangolo.pages.dev |
svlandeg
marked this pull request as ready for review
June 1, 2026 21:01
svlandeg
changed the title
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.
Description
This PR changes the test matrix. Before, it was taking almost 5 minutes for the tests to run with the "lowest-direct" setting on a Windows runner. Increasing the lower bounds helped somewhat, but not enough. That's why this PR moves this particular setting to Mac OS, succesfully getting all tests below 2 minutes.
"Test" timing on "lowest-direct", ✅ indicates the settings used in this PR, ❌ indicates
master(times vary between runs, but this gives a ballpark idea)
It's likely that Windows is particularly slow because new processes use
spawninstead offork, and our test suite has many coverage run / subprocess launches.Bumping
pytest-cov/pytest-sugar/pytest-xdistlower bounds keeps "lowest-direct" viable on pytest 9. The bump uncovered an issue with theget_binary_stderrtest which wasn't calling coverage correctly.AI Disclaimer
No AI used for the edits, only for generating hypotheses / explanations. All experiments & analyses by yours truly.
Checklist