google
Deprecate fuzzzers and ignore fuzzers from CI
- Deprecate the list of fuzzers as discussed.
- Let CI ignore fuzzers that we want to keep but are not yet compatible with Ubuntu20 or Python3.10.
Are we deleting much more than is needed here? For example, wingfuzz doesn't need to be modified? https://github.com/google/fuzzbench/pull/1568
Are we deleting much more than is needed here? For example, wingfuzz doesn't need to be modified? #1568
I don't think we have deleted wingfuzz.
I noticed that it is compatible with the new version and is under active development, so I did not remove it although we did not select it in the previous list.
I think I double-checked that I did not remove any fuzzers we select in that list, but if there is any fuzzer we need to keep, please let me know and I am more than happy to add them back : )
I added back aflplusplus_cmplog and aflplusplus_cmplog_r, as there is a new experiment request of it in the master branch.
Is there any other fuzzers like them (e.g., not in the previous list but should be kept for experiments)?
Thanks! I will add them back.
@jonathanmetzman : Do you happen to know which part of the code affects the CI tests' names?
For example, the first CI test below is named as Build fuzzers / build (afl, klee, oss-fuzz) (pull_request), which has an extra klee between the fuzzer afl and benchmark type oss-ufzz.
I reckon this may relate to the new category I added in fuzzers.yaml, but I was not sure how that affects the name of the CI tests.
I double-checked that the actual command run in each test looks normal. Taking the same example, the first CI is actually running afl on oss-fuzz benchmarks as expected, and does not involve klee at all.
@jonathanmetzman : A friendly ping on this, to continue our discussion this morning : ) The problem is stated above.