jonathanmetzman
jonathanmetzman
Took me all day go from early POC to a version that builds alongside everything else and does bad build check: https://pantheon.corp.google.com/cloud-build/builds;region=us-central1/d16321e9-7e5c-4a80-a681-e34c85f59dbf?project=oss-fuzz
/gcbrun trial_build.py skcms --sanitizer address memory coverage undefined --fuzzing-engine libfuzzer afl honggfuzz --architectures i386 x86_64 aarch64
infra-test failure is known and is a straightforward fix to the test that I will do tomorrow
Failures are unrelated.
I couldn't really find why it's bad to have more layers? Could you explain?
Could you do me a favor and show me what the difference is? If it is negligible I'd rather keep things as is.
> Questions: > > 1. Do we need to have an [`centipede.options` file](https://github.com/google/oss-fuzz/blob/0296d0f3797728063b12efa3be4048476d732c60/infra/base-images/base-runner/run_fuzzer#L52) to store the params that `centipede` needs to run? No. This is supposed to for fuzz targets....
Awesome progress. I wasn't expecting to see this so fast!