You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(scripts): probe reads NOT MEASURED when the baseline run already fails (#15455)
`probeEarlyReturn` awarded HELD/ACCIDENT from the mutated run alone. When the
UNMUTATED file already exits non-zero the tree cannot run it at all, so the
mutation had nothing to defeat -- but both runs exit non-zero and both print a
module-resolution stack, so the mutated run "speaks" and the row read HELD. A
checkout without `pnpm install` therefore reported the flattering answer for
every file it could not load, and the same row read ACCIDENT once installed.
The baseline is now a PRECONDITION, read before any reading of the mutated run:
a non-zero one ends the probe as NOT MEASURED with `baseline run failed
(exit N)`. The mutated run is not spawned at all -- in the shape that motivates
this every row is baseline-red, so those spawns would double a whole sweep to
learn nothing. The row additively publishes `baselineExit`/`baselineBytes`/
`baselineHead`; no existing key is renamed, and `--probe`'s listing and tallies
fold it into the existing NOT MEASURED class.
A new inline control (`UNRUNNABLE_GATE`, an unresolvable import) pins both
halves: the verdict is NOT MEASURED with that reason, and the fixture really is
a red baseline that SPEAKS -- the shape an exit-code-and-speech reading scored
HELD.
Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk
Co-authored-by: Claude <noreply@anthropic.com>
`POSITIVE CONTROL FAILED: the accident fixture no longer produces the measured shape (exit ${a.mutatedExit}, ${a.mutatedBytes} byte(s)); the ACCIDENT verdict above would then be passing for the wrong reason`);
498
+
// The precondition, in the direction that matters: a baseline that already
499
+
// failed ends the probe, and it must end it as NOT MEASURED -- never as the
500
+
// HELD an exit-code-and-speech reading would award it (#15391).
`POSITIVE CONTROL FAILED: a file whose BASELINE run already exits non-zero was read as ${u.verdict} (${u.why??''}); the mutation had nothing to defeat, so nothing was measured`);
503
+
// ... and for the RIGHT reason: this fixture has to be the flattering shape,
504
+
// a red baseline that SPEAKS. A fixture that fell silent, or that stopped
505
+
// being red, would satisfy the verdict above while testing nothing.
`POSITIVE CONTROL FAILED: the unrunnable fixture no longer produces the measured shape (baseline exit ${u.baselineExit}, ${u.baselineBytes} byte(s)); the NOT MEASURED verdict above would then be passing for the wrong reason`);
0 commit comments