fix(benchmark): an accuracy run that produces no number must fail - #454
Open
leopck wants to merge 1 commit into
Open
fix(benchmark): an accuracy run that produces no number must fail#454leopck wants to merge 1 commit into
leopck wants to merge 1 commit into
Conversation
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
github-actions
Bot
added
the
size/normal
leopck
force-pushed
the
fix/acc-no-score-is-failure
branch
from
August 19, 2026 13:53
e3ee97c to
8ba6509
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #454 +/- ##
=======================================
Coverage ? 81.01%
=======================================
Files ? 150
Lines ? 20224
Branches ? 0
=======================================
Hits ? 16384
Misses ? 3840
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
An accuracy run could complete every unit of work, exit 0, and report `N/A`. `finalize_benchmark()` scored, wrote `accuracy_results.json` with `score: null`, printed the summary, and returned -- so `main.py` exited 0 and every wrapper downstream read the run as a pass. This is not hypothetical. A distributed SWE-bench run drove all 20 of its units to terminal records; 17 were abandoned to infrastructure failures, the merge gate correctly refused, `score()` returned None -- and the sbatch wrapper wrote `disposition=run completed (driver rc=0, results=20/20)` over a run with no accuracy number at all. rc=0, all work "done", no number is the failure shape that costs whole GPU allocations, so make it loud where it originates instead of asking each caller to notice. `_require_accuracy_numbers()` runs last, after every artifact is on disk, so the failure never costs the evidence needed to diagnose it. A real number flagged `complete=False` (a partial headline) still passes: the number exists and the entry already says it is partial. A PERF-mode run owes nothing for an externally-scored dataset it never dispatched. Also count what was evaluated, not what was loaded, in the accuracy-only summary line: SWE-bench Verified loads all 500 rows and scores `num_instances` of them, so the run above printed "500 samples evaluated" directly beneath its own "unit=200" headline.
leopck
force-pushed
the
fix/acc-no-score-is-failure
branch
from
August 20, 2026 16:12
8ba6509 to
63e1a38
Compare
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An accuracy run could complete every unit of work, exit 0, and report
N/A.finalize_benchmark()scored, wroteaccuracy_results.jsonwithscore: null, printed the summary, and returned -- somain.pyexited 0 and every wrapper downstream read the run as a pass.This is not hypothetical. A distributed SWE-bench run drove all 20 of its units to terminal records; 17 were abandoned to infrastructure failures, the merge gate correctly refused,
score()returned None -- and the sbatch wrapper wrotedisposition=run completed (driver rc=0, results=20/20)over a run with no accuracy number at all. rc=0, all work "done", no number is the failure shape that costs whole GPU allocations, so make it loud where it originates instead of asking each caller to notice._require_accuracy_numbers()runs last, after every artifact is on disk, so the failure never costs the evidence needed to diagnose it. A real number flaggedcomplete=False(a partial headline) still passes: the number exists and the entry already says it is partial. A PERF-mode run owes nothing for an externally-scored dataset it never dispatched.Also count what was evaluated, not what was loaded, in the accuracy-only summary line: SWE-bench Verified loads all 500 rows and scores
num_instancesof them, so the run above printed "500 samples evaluated" directly beneath its own "unit=200" headline.What does this PR do?
Type of change