FAILURE MAP
← Case archive

FA-84143 / Sports scoring and tiebreakers / Member archive

Extra-inning games never become final · case 03

A game decided in the tenth inning stays in progress.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Game status from a line score. away and home list runs per inning; home has either the same number of entries as away or one fewer (bottom half not yet played), otherwise return "invalid". When home is one short: if at least scheduled innings have started and home leads, the game is final (home wins without batting); otherwise in progress. When equal length: if at least scheduled innings are complete and the score is not tied, the game is final; ties continue into extra innings. Return ["final", "home"/"away", innings] or ["in progress", None, None].

Why this case matters

Scoreboards and settlement engines decide when a baseball game is official and who won.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
control away wins in ten["in progress", null, null]["final", "away", 10]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗