Skip to content

fix: eval scores acceptance lines by case id and fails on a nonzero acceptance exit - #73

Merged
alsoknownaswill merged 1 commit into
mainfrom
pub-eval-suffix
Nov 3, 2026
Merged

alsoknownaswill merged 1 commit into
mainfrom
pub-eval-suffix

Conversation

@alsoknownaswill

@alsoknownaswill alsoknownaswill commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

The eval harness tagged each acceptance line with the reviewer name when several reviewers run, so lines did not match case ids and scored as missing.

The eval now strips the longest reviewer name that ends the tag, keeps the worst outcome per case, and scores a case a reviewer did not report as missing. Checks 1 and 2 also fail when the acceptance run exits nonzero. A hold for a human on a clean control is still a false alarm, and a size hold never counts as correct.

Tests cover the suffix parsing, worst-outcome ordering, missing cases and the exit code.

…ro exit of the acceptance run

With several reviewers run.ts tags each line with the case id and the reviewer
name. The eval strips the longest reviewer name that ends the tag, keeps the worst
outcome per case, scores a case a reviewer did not report as MISSING, and fails
checks 1 and 2 when the acceptance run exits nonzero. A hold for a human on a
clean control is still a false alarm.
@alsoknownaswill alsoknownaswill changed the title fix: eval scores acceptance lines by case id; size-cap holds on clean controls count as correct fix: eval scores acceptance lines by case id and fails on a nonzero acceptance exit Nov 3, 2026
@alsoknownaswill
alsoknownaswill merged commit e836326 into main Nov 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant