Repository navigation
fix(ci): route the moved mutation-pilot configs to the core job - #2983
Merged
Merged
Conversation
#2957 moved stryker.config.mjs and vitest.mutation.config.ts from the repository root into test-policy/. At the root they were unclassified paths and planned full CI. Under test-policy/ they match the rule for the test policy files the build job checks, which selects no lane. The core job runs both through `pnpm test:mutation`, so the load-closure guard added by #2920 fails on testnet-canary: tornado_core loads test-policy/stryker.config.mjs via ci.yml tornado-core > test:mutation A rule ahead of the test-policy/ one routes the two configs to tornado_core. The rest of test-policy/ is unchanged. A test pins both files to the core lane and keeps vitest.properties.config.ts, which no CI job runs, on the build job alone. Repository-script tests: 435 pass (434 with one failure before this change). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
otReviewAgent
left a comment
otReviewAgent
left a comment
There was a problem hiding this comment.
Review Agent completed this review and found no issues.
branarakic
approved these changes
Oct 2, 2026
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
testnet-canary fails the repository-script tests since #2920 and #2957 both landed. Each passed on its own; together they break the load-closure guard:
#2957 moved
stryker.config.mjsandvitest.mutation.config.tsfrom the repository root intotest-policy/. At the root they were unclassified paths, which plan full CI. Undertest-policy/they match the rule for the policy files the build job checks, which selects no lane. But the core job runs both throughpnpm test:mutation, so #2920's guard (merged just before) requires a change to them to selecttornado_core.Every PR's CI runs on its merge with canary, so this failure shows up in the "Build packages" job, and therefore the CI gate, of every open PR until it is fixed.
Change
scripts/lib/ci-routing.mjs: a rule ahead of thetest-policy/one routestest-policy/stryker.config.mjsandtest-policy/vitest.mutation.config.tstotornado_core. The rest oftest-policy/is unchanged.scripts/lib/__tests__/ci-delta-routing.test.mjs: a test pins both files to the core lane and keepstest-policy/vitest.properties.config.ts, which no CI job runs, on the build job alone.Verification
node --test scripts/lib/__tests__/ci-delta-routing.test.mjspnpm run test:scriptspnpm run lint🤖 Generated with Claude Code