mlcommons / mlcommons/modelbench
Fix inaccurate response count in metadata output of run-job
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 134
- Forks
- 36
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 17
Description
This issue has no description.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names run-job and its metadata output but gives no file, reproduction steps, or expected count. Start by locating the run-job entry point and the code that produces the metadata, then compare the reported response count with the underlying results. Done means the metadata reports the accurate response count and the behavior is covered by an appropriate test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100