Provide mismatch information in fuzz check
Open
area/ci
area/fuzzing
enhancement
no stalebot
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
Description
Currently the fuzz precheck is pretty crude, just counting how many network filters should be robust to downstream, and comparing that to the number listed for fuzzing
This doesnt provide very useful information if the check fails, and it shouldnt be too difficult to update the check to compare the sets and tell the user any difference
Contributor guide
Assessment
This issue has not been assessed yet.