Broken llvm build

[Dor1s]

https://oss-fuzz-build-logs.storage.googleapis.com/index.html

Step #4: ++ sancov -print-coverage-pcs /workspace/out/address/clang-fuzzer
Step #4: ++ wc -l
Step #4: BAD BUILD: the code does not seem to have coverage instrumentation.
Step #4: + local NUMBER_OF_EDGES=0
Step #4: + ((  0 < 90  ))
Step #4: + echo 'BAD BUILD: the code does not seem to have coverage instrumentation.'
Step #4: + CHECK_FAILED=1
Step #4: + ((  1 > 0  ))
Step #4: + exit 1

[kcc]

That's a special case :(
The LLVM build uses fresh llvm and flags that are different from what we currently use in oss-fuzz.
(The new stuff is -fsaintize=fuzzer)

[kcc]

Hm. Is this check failing the llvm build now? It shouldn't...

[Dor1s]

Just checked the most recent build: https://storage.cloud.google.com/clusterfuzz-builds/llvm/llvm-address-201709080449.zip?_ga=2.98069855.-192946872.1496676137

sancov -print-coverage-pcs doesn't print anything for both clang-fuzzer and llvm-dwarfdump-fuzzer.

Maybe we should wait for the next clang roll on Chromium side. There was a roll today up to https://reviews.llvm.org/rL312679, before that we've been using https://reviews.llvm.org/rL310694 which is one month old...

[kcc]

Yes, see my comment above (special case).
We need
#832 (needs clang roll)
and
https://bugs.llvm.org/show_bug.cgi?id=34314 (needs our work)
to make it work again in oss-fuzz.

[morehouse]

LLVM build has been green for a long time.