FA-83985 / Sports scoring and tiebreakers / Member archive

Zero-overs guard checks the wrong totals · case 05

A table with no completed deliveries raises or reports a bogus rate.

Member previewVariant 5 · 3 implementations · 9 checks per implementation

Case contract

Tournament net run rate. Each match row is [runs_for, overs_faced, all_out_for, runs_against, overs_bowled, all_out_against]. Overs strings use cricket notation "O.B" where B is balls 0-5 ("43.4" = 43 overs 4 balls); a ball digit above 5 returns "invalid overs". When a side was all out its innings counts as the full quota of overs. NRR = total runs for / total overs faced - total runs against / total overs bowled, aggregated over all matches before dividing, formatted as "%+.3f" of the exact value. If either overs total is zero return "no overs".

Why this case matters

Group-stage standings use net run rate as the first tiebreaker after points.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: zero overs guard	`"raised ZeroDivisionError"`	`"no overs"`	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.