No fuzzer stats on aptos-core

[gedigi]

The infrastructure is not producing data for our fuzzers since August 6th. We had build issues but they have been solved and the build has now completed for the last 2 days (ref).

Can you help understand what's missing/broken?

[DavidKorczynski]

I think this is related to https://github.com/google/oss-fuzz/issues/12357 https://github.com/google/oss-fuzz/issues/12349

[gedigi]

I think this is related to #12357 #12349

I see, thanks - so is it being addressed on the infrastructure side?

[DavidKorczynski]

yes, I think give this a few days and it should stabilize

[catenacyber]

I also have the same issue on ngolo-fuzzing since March : just a few stats (like 10 targets our of 100), and coverage build not working because it does not find corpus. Locally, it seems to work fine so far.

Any clues ?

[catenacyber]

cf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67724#c18

[maflcko]

I also have the same issue on ngolo-fuzzing since March : just a few stats (like 10 targets our of 100), and coverage build not working because it does not find corpus.

Not sure if related, but for bitcoin-core there was a similar issue: https://github.com/google/oss-fuzz/issues/12142

[DavidKorczynski]

I also have the same issue on ngolo-fuzzing since March

Considering this has happened for several months then I don't think the underlying issue is the infra issues I have in mind.

@jonathanmetzman @oliverchang do you have ideas?

[catenacyber]

Running out of disk space is likely since this is a big project (many fuzz targets)

[jonathanmetzman]

I bumped up disk size to 80 GB. Might be worth waiting to land that PR.

[catenacyber]

Thanks Johnathan, it looks better now :-)

[catenacyber]

Thanks Johnathan, it looks better now :-)

And finding bugs again https://github.com/golang/go/issues/69066

[maflcko]

I think this one is fixed, given that https://github.com/google/oss-fuzz/pull/12379#event-13940750006 is closed?