Stop the advisory match line claiming a failure count nobody measured #247

Merged
JMR-dev merged 1 commits from fix/api37-report-match-line into main 2026-09-06 14:11:24 +00:00
JMR-dev commented 2026-09-06 14:03:43 +00:00 (Migrated from github.com)

Left behind by #245: auto-merge fired on the head before this commit's push registered, so the
fix is on the branch and not on main. Same commit, nothing added.

#245's own advisory leg is what caught it. With five markers and a truncated run it printed

  failed:            4
  ...
  baseline: matches (5 expected, 5 failed)

three lines apart. That line has always printed the baseline twice, which was true while failed
had to equal it to reach the line at all — and #245 removed that requirement for truncated runs
without noticing this line depended on it. A truncated run now reads

  baseline: matches (5 expected; 4 of 5 failed, on a run the abort truncated — not compared)

Pinned by a third case in e2e-report-shape-test.sh, beside the two #245 added.

🤖 Generated with Claude Code

Left behind by #245: auto-merge fired on the head before this commit's push registered, so the fix is on the branch and not on `main`. Same commit, nothing added. #245's own advisory leg is what caught it. With five markers and a truncated run it printed ``` failed: 4 ... baseline: matches (5 expected, 5 failed) ``` three lines apart. That line has always printed the baseline twice, which was true while `failed` had to equal it to reach the line at all — and #245 removed that requirement for truncated runs without noticing this line depended on it. A truncated run now reads ``` baseline: matches (5 expected; 4 of 5 failed, on a run the abort truncated — not compared) ``` Pinned by a third case in `e2e-report-shape-test.sh`, beside the two #245 added. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.