OpenHands / OpenHands/benchmarks
Commit0: bug 526 impact on old results
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 124
- Forks
- 90
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 1
Description
This issue tracks the impact of #526 on old evaluation results for Commit0.
We analyzed the commit0 results from https://github.com/OpenHands/openhands-index-results/tree/main/results for cachetools and parsel to see if they had errors that marked them as unresolved due to the test command issues.
Here are the results:
| Model Name | cachetools error | parsel error |
|---|---|---|
| DeepSeek-V3.2-Reasoner | No | Yes (exit code 127) |
| GLM-4.7 | Yes (exit code 1, likely ImportError) | No |
| GLM-5 | Yes (exit code 1, likely ImportError) | No |
| GPT-5.2 | No | Yes (exit code 127) |
| GPT-5.2-Codex | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| GPT-5.4 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Gemini-3-Flash | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Gemini-3-Pro | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Gemini-3.1-Pro | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Kimi-K2-Thinking | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Kimi-K2.5 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| MiniMax-M2.1 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| MiniMax-M2.5 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Nemotron-3-Nano | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Qwen3-Coder-480B | No | No |
| Qwen3-Coder-Next | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| Qwen3.5-Flash | Yes (exit code 1, likely ImportError) | No |
| claude-opus-4-5 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| claude-opus-4-6 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| claude-sonnet-4-5 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
| claude-sonnet-4-6 | Yes (exit code 1, likely ImportError) | Yes (exit code 127) |
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
Start with the Commit0 results for cachetools and parsel in the linked openhands-index-results repository, then review issue #526 and the listed exit codes. Done means documenting which old evaluations were affected and how their unresolved status should be interpreted; the issue does not name a source file or test to modify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100