You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
It seems the coverage build is failing to fetch the corpus, as the failure message says something like this for all targets:
Is it similar to #4937? If yes, I am not sure how it was resolved then!
The text was updated successfully, but these errors were encountered: