Repository navigation
fix(ci): register missing mutation coverage tests - #17083
diegosouzapw wants to merge 2 commits into
Conversation
|
Exact-candidate checkpoint, 2026-10-18: HOLD — not merge-ready. Current head An independent focused reproduction on the owner-approved validation VPS, Relay's403/429 failure did not reproduce in that focused run. The context-retention Coordination: #17090 from another workstream addresses the three catalog failures The earlier focused registration tests remain valid for their limited scope. |
CI Coverage Report
Coverage artifact was not available for this run. |
|
Superseded by #17090, which registered the same four tests (chat-empty-stream-recovery, content-policy-refusal, provider-error-rules-opt-in-flags-16797, stream-timing-late-output) in stryker.conf.json tap.testFiles. Nothing left to land. |
Summary
Register four existing covering test files in Stryker's explicit
tap.testFileslist. The strict gate found seven missing test/module associations across five
mutated modules on release base
a016744417facc740a9360816a00dca07d72d6c6.No runtime behavior, mutation targets, thresholds, exemptions or test assertions
are changed.
registration failure, not all release failures.
Validation on VPS .15
Node 24.20.0; isolated worktree and temporary test data; reused diagnostic
dependencies, not a fresh-install certificate.
node scripts/check/check-mutation-test-coverage.mjs --strict— exit 1;6,948 unit files, 31 mutated modules, seven missing associations.
node --import tsx/esm --import ./tests/_setup/isolateDataDir.ts --test --test-concurrency=1 tests/unit/build/check-mutation-test-coverage.test.ts tests/unit/chat-empty-stream-recovery.test.ts tests/unit/content-policy-refusal.test.ts tests/unit/provider-error-rules-opt-in-flags-16797.test.ts tests/unit/stream-timing-late-output.test.ts— 65 PASS, zero failures/skips/cancellations.
RED/GREEN and regression receipts preserve source/diff/lockfile identities,
resource reserves, actual exits and raw-log digests. Source remained unchanged
during each check. The exact configuration content reviewed and tested is SHA256
f691461e8b62dd516276a217bea7da168fc24c736d1afd3f92c0a999a43a4cf6.Full mutation scoring, full CI/release admission, build and deployment are
separate and are not claimed by these focused results. Owner-authorized merge
remains conditional on all applicable exact-candidate requirements.