test(port/oracle): remove mutation-e2e canary suite - #681
Merged
Conversation
The end-to-end mutation pipeline suite (patch built dist/server → boot mutated servers → prove the oracle goes red → rebuild pristine) is removed per user direction: it is time-consuming (rebuilds dist inside the test suite) and its safety-net value does not justify the maintenance cost. Its pristine-rebuild step has been broken anyway (red) since the buildinfo relocation in 1de2258, so it was no longer catching anything — just failing. The lighter data-level mutation-validation suite stays: it checks mutation detection at the data layer without booting servers or rebuilding dist. Closes kata 140h.
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
1 participant
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
Removes
test/unit/port/oracle/mutation-e2e.test.ts— the end-to-end mutation pipeline suite that patches builtdist/server/**, boots mutated servers, asserts the oracle goes red, and rebuilds dist from pristine source.Why
Per user direction: the suite is time-consuming (it rebuilds
distmid-run, in the unit suite) and its safety-net value doesn't justify the maintenance cost. It has additionally been red since the buildinfo relocation in1de2258d8broke its pristine-rebuild step — it hasn't caught anything in a while, it has just been failing.The lighter data-level
mutation-validation.test.tsthis suite was built on top of is kept — it checks mutation detection without booting servers or rebuildingdist.No other references to
mutation-e2eexist in configs, CI, or scripts (verified by grep).Verification
npm run test:oracle— 5 passed / 3 skipped files, all 109+ tests green, on the branch (the one mid-run failure under parallel machine load,t1-batch-equivalence-rust, was rerun green on a quiet machine).amplifier-session-locatorjitter test; passes 19/19 rerun solo, also seedable for the existingep0fdeflake kata).Closes kata 140h.