JosephFerano/flan
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

The measured baselines, and why a survey that says 143 is not a regression

Browse Source
This commit is contained in:
Joseph Ferano 2026-09-13 23:41:52 +07:00
parent f9f37e524a
commit 3eb53d0f85
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
HANDOFF-devtest-noise.md
View File

@ -83,8 +83,17 @@ should be reading on a green run.
passes. The `Some "16"` expectation was temporarily changed to a value it cannot match, the block failed, and the
captured stderr — the linker's own words — was reprinted under its header. Then reverted.
Baseline not regressed: `dune test --root .` exit 0, `spike/x86/survey.sh` 101 MATCH / 0 DIFFER / 0 refused,
`spike/x86/cells.sh` 4/4.
Baseline not regressed, all three measured after the change:
- `dune test --root .` — exit 0.
- `spike/x86/survey.sh` — **101 MATCH / 0 DIFFER / 0 REFUSED / 0 NOX86**, 36 skipped (28 does-not-compile, 6 no-main,
2 runs-forever).
- `spike/x86/cells.sh` — **4/4**, exit 0.
One thing not to re-derive: a first attempt at the survey came back `SURVEY_EXIT=143` with a bare `Terminated`. That
was the harness killing the process group of a long background command, not a survey failure and nothing to do with
this change — nothing under `lib/` was touched. Re-run detached under `setsid` it is 101/0/0. A `143` from that
script means it was signalled; read it as "run it again", not as a regression.
## One stale note left behind, deliberately not edited