jonathanmetzman

> Would it make sense to make this a more general "filesize > N kb" check? E.g. I noticed https://github.com/google/oss-fuzz/tree/master/projects/woff2/corpus has a non-zip corpus with one file being ~600kb. It...

/gcbrun trial_build.py skcms --sanitizer address memory undefined coverage --fuzzing-engine libfuzzer afl honggfuzz

> I created a [minimal jvm fuzzing project](https://github.com/johannes-riecken/java-example/runs/6817999306?check_suite_focus=true). While the fuzzing happens, the step to generate a coverage report is skipped, which shouldn't happen as I set `fail-fast: false` in...

Because you aren't building the fuzzers in a place where the coverage step has access to it. Add that step. It would be better if you used the provided examples.

This might work, but it really would be best if the docs were followed exactly ``` name: CIFuzz on: push: branches: [master] pull_request: # The branches below must be a...

You can try the configuration [i provided above](https://github.com/google/oss-fuzz/issues/7839#issuecomment-1152408614) or do exactly as specified in the documentation (that means don't merge anything).

Does the config I provided above work? >So the documentation tells me to merge it and in my opinion merging or not merging should both work It says to merge...

The initial example did omit a build fuzzers step: https://github.com/johannes-riecken/java-example/actions/runs/2473242038/workflow I don't think I have time to clone your repo and play around. Is there anything else that's still broken?

> @jonathanmetzman can you provide more details here on what's going wrong and how we can fix it? FuzzBench assumes that every trial finishes. When you give it fuzzers that...

Yeah basically the problem is we only generate the report once, after completion. This is fragile and in #1491 we see experiment measuring is prone to not completing.