More debug information in general (especailly for failing tests)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 21
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
- [ ] DVSim config
- [ ] Seeds for failing tests so they can be reproduced locally
- [ ] Logs per test
- [ ] Full tool version for reproducibility
- [ ] Tool command ran (i.e. JobSpec)
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 no files, tests, or entry points. Start by locating DVSim's test-failure reporting and output-generation paths, then trace where configuration, seeds, logs, tool versions, and JobSpec commands are available. Done means the requested debug information is captured for failing tests and can support local reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100