Repository navigation
ci: run the Python test matrix as parallel jobs - #75
Merged
Merged
Conversation
Split the single serial `build` job into `tag-check`, `checks`, one `test` job per Python (3.11-3.14), and a final `build` job that packages only after everything passes. Coverage is measured on 3.14 only. `build` stays the required status check: it runs under `!cancelled()` and fails itself if an upstream job failed, because a skipped required check would otherwise count as passing.
dfkunstler
force-pushed
the
ci/parallel-test-matrix
branch
from
November 17, 2026 11:48
fb42c37 to
9dde316
Compare
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
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.
Summary
buildjob intotag-check,checks(generate, drift check, lint, typing, security, docs), onetest (3.11|3.12|3.13|3.14)job per Python, and a finalbuildjob that packages only after all pass.coverage-html.buildstays the required check. It runs under!cancelled()and fails itself if an upstream job failed, since a skipped required check counts as passing.models.py; the drift check inchecksties it to the generated file.DEVELOPING.mdupdated to describe the new job layout.Timing (wall clock, per CI run)
mainruns): about 4.7 to 6.7 min.No library code changed, so there are no performance numbers for PERFORMANCE.md.
Notes
build.ymlandpyproject.toml; both carry a comment to keep them in step.