[QEMU] Coverage reports are not produced since Nov 2023
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12.7k
- Forks
- 2.9k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 62
Description
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the coverage build step that fetches and unpacks the QEMU fuzzing corpus, then compare the failure with issue #4937. The work is done when the corpus is fetched successfully and coverage reports are produced for all affected targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100