Repository navigation
fix: validate issued samples against the recorded dataset size - #171
Open
kaulastudies wants to merge 2 commits into
Open
kaulastudies wants to merge 2 commits into
kaulastudies wants to merge 2 commits into
Conversation
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
There was a problem hiding this comment.
🟡 Changes recommended
Explicitly reported zero or negative n_samples_issued values bypass the required positivity error when dataset size is unavailable, producing only an unknown-size warning.
1 open issue
What changed in this PR
This PR addresses #167 by adding whole-dataset-pass validation to the submission checker using the recorded dataset size, without changing minimum-completed-query enforcement.
Changes:
- Adds an optional, positive
n_samples_from_datasetsetting and issued-count validation. - Adds diagnostics and regression tests for whole passes, partial passes, non-positive counts, and missing metadata.
- Documents the recorded size and the remaining manual checks for full-dataset use or approved subsets.
| File | Description |
|---|---|
| tests/submission_checker/test_sample_multiples.py | Adds regression coverage for pass counts and missing metadata. |
| src/submission_checker/models/file/point_config.py | Defines the positive, optional dataset-size field. |
| src/submission_checker/models/aggregate/point_result.py | Adds validation against the recorded dataset size. |
| src/submission_checker/data/messages.yaml | Adds validation results and corrective guidance. |
| docs/endpoints-submission-cli.md | Explains size recording and subset-approval responsibilities. |
Review effort: Balanced
anandhu-eng
marked this pull request as ready for review
November 9, 2026 07:10
Contributor
Author
|
@anandhu-eng The issued-count fix is in b03da4d, and the review thread is resolved. GitHub now shows all seven checks passing. Could you take another look when you have time? |
This branch has not been deployed
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
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.

Addresses #167.
Adds a whole-pass check using
runtime_settings.n_samples_from_datasetfrom the resolved benchmark settings. Explicitly supplied zero or negative issued counts are errors even when the dataset size is unavailable. Partial passes are errors when the size is known. An omitted issued count, or a positive count with no dataset size, produces an explicit warning. The dataset-size field must be positive when supplied.The minimum-query table is deliberately not used as dataset size: some accuracy counts include repeats, and LiveCodeBench's per-model run shape differs from that table. The guide explains the recorded field and makes clear that reviewers still need to verify full-dataset use or working-group approval for a subset. Existing minimum-completed-query enforcement is unchanged.
Validation for
b03da4don Python 3.12:744e040and pass with this fix.#170 is merged, and this PR has been marked ready for review by a maintainer. It has no dependency on #170.
Thanks to @nv-alicheng for reporting the gap. Prepared with Codex assistance; the local checks above were executed.