skia: UBSan build is crashing on seed corpus

[Dor1s]

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

5 fuzz targets are considered broken as they crash when running on a seed corpus without any mutations.

//cc @kjlubick

[kjlubick]

Is this new? Can we opt out?

[inferno-chromium]

@kjlubick - yes that check is a little noisy without auto-bug creation (esp here vs monorail). we are disabling the check now.

[Dor1s]

Yes, the post-build check is new, but the idea is not, as it matches requirements of Ideal Integration Guide. There is no way to opt out. Fuzz targets that crash on seed corpus are considered broken and not useful until those crashes get fixed. If we upload and run such targets, we'd simply waste CPUs while crashing on corpus again and again.

However, we've temporarily disabled that check until we implement bug auto-filing for broken builds.

[kjlubick]

Thanks - will the autobug give a list of bad inputs to make it easy to remove from the corpus? Or will there be a script I can run locally to double check the seed corpus is clean?

[Dor1s]

Removing inputs from the corpus is a wrong way to fix this :)

But yes there will be a way to reproduce that locally: #1356

[inferno-chromium]

No need to track here, you should see a bug filed with title ": Build failure" in monorail tracker.