[QEMU] Coverage reports are not produced since Nov 2023

[Navidem]

It seems the coverage build is failing to fetch the corpus, as the failure message says something like this for all targets:

Step #5: unzip:  cannot find zipfile directory in one of /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip or
Step #5:         /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip.zip, and cannot find /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip.ZIP, period.
Step #5: Failed to unpack the corpus for qemu-fuzz-i386-target-generic-fuzz-virtio-blk. This usually means that corpus backup for a particular fuzz target does not exist. If a fuzz target was added in the last 24 hours, please wait one more day. Otherwise, something is wrong with the fuzz target or the infrastructure, and corpus pruning task does not finish successfully.

Is it similar to #4937? If yes, I am not sure how it was resolved then!

[jonathanmetzman]

It seems the coverage build is failing to fetch the corpus, as the failure message says something like this for all targets:

Step #5: unzip:  cannot find zipfile directory in one of /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip or
Step #5:         /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip.zip, and cannot find /corpus/qemu-fuzz-i386-target-generic-fuzz-virtio-blk.zip.ZIP, period.
Step #5: Failed to unpack the corpus for qemu-fuzz-i386-target-generic-fuzz-virtio-blk. This usually means that corpus backup for a particular fuzz target does not exist. If a fuzz target was added in the last 24 hours, please wait one more day. Otherwise, something is wrong with the fuzz target or the infrastructure, and corpus pruning task does not finish successfully.

Is it similar to #4937? If yes, I am not sure how it was resolved then!

Exactly, I think no corpus means no coverage report.

[Navidem]

Exactly, I think no corpus means no coverage report.

How can we fix the corpus issue? I was able to download from gs://qemu-corpus.clusterfuzz-external.appspot.com/libFuzzer/ but the backup seems broken.

[a1xndr]

I think last time we discussed, it seemed merge-jobs were failing. Since then I cleaned up a lot of the fuzzers, but the jobs never started working again. It is very strange because I have confidence that at least some of the targets do not crash/timeout yet coverage reports are not generated for any targets. It seems like when they initially broke, it forced the project into some sort of broken state permanently