ci(repo): consolidate mutation runners and gate the score - #140
Open
systemfsoftware-maker wants to merge 6 commits into
Open
ci(repo): consolidate mutation runners and gate the score#140systemfsoftware-maker wants to merge 6 commits into
systemfsoftware-maker wants to merge 6 commits into
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
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.
What
Reworks
.github/workflows/mutation.ymlso the ~25 mutation packages run on a handful of runner machines instead of one per package, while keeping both incremental mechanisms and making the mutation score gate PRs.Changes
discoverchunks sorted packages into groups of 5, emittingbuckets+package_count;mutationmatrix iterates buckets, runningturbo mutationwith--concurrency=2 --continue=dependencies-successful)..turbo/cacheunder a mutation-specific per-bucket key (turbo-mutation-<os>-<bucket>-<sha>) so it never collides with the check job'sturbo-...key on the same commit.bucket-incremental/, re-keyed tostryker-incremental-<bucket>-main.continue-on-error: truefrom the mutation step, so a package below its break threshold fails the check (reverses the prior advisory posture).scripts/tools/merge-mutation-reports.mjsreadPartsnow discovers parts recursively so the aggregate report spans every bucket.AGENTS.mdREPO-D1 updated: CI's Mutation workflow now gates on the score too.Decisions (settled with user)
Verification
pnpm check:localexits 0 (run after the rebase ontomain).pnpm check:turbo-graphclean;guard-action-provenanceclean.merge-mutation-reports.mjs --selftestpasses (8 fixtures); recursivereadPartssmoke-tested against a synthetic 2-bucket/3-package layout (merges 3 of 3, aggregate**all**row at 100.00).turbo mutation --filter=./packages/oxlint-plugins/effect-store --dry=jsonconfirms the volatilereports/stryker-incremental.jsoninput is gone (0 incremental files in inputs).