Failed coverage building for cups-filters
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- build-system, testing
Research direction
Start with the reproduction commands in the issue, especially the coverage step for cups-filters, and inspect the fuzzpdf corpus warning in the build logs. Determine why the coverage build cannot unpack the corpus while address and memory builds succeed. Done means the coverage report completes without the empty-corpus failure.
Written by the indexing model from the issue text.
Description
he latest building of coverage sanitizer for cups-filters has failed.
The build logs are as follows:
Finished Step #4
Starting Step #5
Step #5: Already have image (with digest): gcr.io/oss-fuzz-base/base-runner
Step #5: warning [/corpus/fuzzpdf.zip]: zipfile is empty
Step #5: Failed to unpack the corpus for fuzzpdf. 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.
Step #5: ********************************************************************************
Step #5: Code coverage report generation failed.
Step #5: To reproduce, run:
Step #5: python infra/helper.py build_image cups-filters
Step #5: python infra/helper.py build_fuzzers --sanitizer coverage cups-filters
Step #5: python infra/helper.py coverage cups-filters
Step #5: ********************************************************************************
Finished Step #5
ERROR
ERROR: build step 5 "gcr.io/oss-fuzz-base/base-runner" failed: step exited with non-zero status: 1
The primary issue seems to be the absence of the fuzz corpus files. I suppose this is due to some keyword filtering specific to the coverage sanitizer build process, as builds and tests for address and memory sanitizers have been successful. Investigating...
- Dominant language
- C
- Stars
- 8
- Forks
- 18
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from OpenPrinting/fuzzing
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
OpenPrinting/fuzzing#45 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
OpenPrinting/fuzzing#47 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
OpenPrinting/fuzzing#46 ·
-
Memory allocation/deallocation mismatch in fuzz_array.c causes immediate crash with AddressSanitizer Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
OpenPrinting/fuzzing#43 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 35/100
OpenPrinting/fuzzing#7 ·
All issues in OpenPrinting/fuzzing
Similar issues
-
internal.h中，漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·