WebAssembly / WebAssembly/binaryen
Automate reduction from fuzz_opt.py
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
If we could automatically run wasm-reduce on a failing testcase that might save a bunch of time. it would need to be specific for each TestcaseHandler, though, so basically a .reduce() method that if it exists we could call it. Then the output of the fuzzer finding a failing testcase could also include the reduced testcase.
Also reducing the command itself could be useful (getting rid of unnecessary passes, etc.).
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 by reading fuzz_opt.py and the TestcaseHandler flow to understand how failing testcases are reported. Investigate how wasm-reduce could be invoked for handlers that support reduction, and consider the separate command-reduction idea. Done should include reduced failing testcases in fuzzer output, with the intended handler-specific behavior defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- compilers, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100