rust-lang / rust-lang/rust-bindgen
Allow specifying a max number of iterations to run in csmith-fuzzing/driver
Open
Nobody has claimed this yet.
A-csmith
A-testing
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
After N iterations have run, the script should exit.
Then, once we are pretty reliably handling csmith's test cases, we can start running N iterations in CI.
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 csmith-fuzzing/driver and trace how the fuzzing loop currently decides when to continue. Add a way to stop after N iterations, then verify that the script exits after exactly that limit and can support fixed iteration counts for CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100