Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QEMU] Coverage reports are not produced since Nov 2023 #12478

Open
Navidem opened this issue Sep 11, 2024 · 2 comments
Open

[QEMU] Coverage reports are not produced since Nov 2023 #12478

Navidem opened this issue Sep 11, 2024 · 2 comments

Comments

@Navidem
Copy link
Contributor

Navidem commented Sep 11, 2024

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
Copy link
Contributor

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
Copy link
Contributor Author

Navidem commented Sep 18, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants