Philipp Görz
Philipp Görz
Hello @AndreasFuchsTPM, thank you for offering to help. > Yes, main_repo makes absolutely no sense to point to tsruk namespace, should be our namespace here. > This would also explain...
@DavidKorczynski I think something went wrong with the command? ``` Starting Step #1 Step #1: Already have image: gcr.io/oss-fuzz-base/trial-build Step #1: INFO:root:Command: ['--sanitizer', 'coverage', '--fuzzing-engine', 'libfuzzer', '--repo', 'https://github.com/phi-go/oss-fuzz', '--branch', 'push-qnznzrmxrksp']....
@DavidKorczynski it seems the branch was not up to date > Needs /gcbrun(https://github.com/google/oss-fuzz/commit/b094c0b06c060459bbcd89b00d662c8bc7f54f6c) to run latest commit
Seems this one timed out before doing any fuzzing or coverage measurements?
All errors seem to be a missing corpus. Unfortunately these errors seem to be unrelated to this change, I don't think I can really do anything here. > Starting Step...
Actually, it seems these missing corpus are a larger issues. Spot checking projects on the fuzz-introspector overview they all seem to fail building coverage.
I added a PR to update the docs here https://github.com/google/oss-fuzz/pull/12955
Yes, fair point. However, to my understanding oss-fuzz mostly uses libFuzzer where this is not available. Nor is it easy to extract where exactly this instability happens for the afl...
@DavidKorczynski is this a policy question or does this just need an implementation? If it just requires implementation and if you can give me pointer where this would be best...