v6 produces empty coverage report
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Start with the CI upload step that changes from codecov/codecov-action@v5 to @v6, then reproduce the same workflow with each version and compare the upload logs and Codecov processing result. Done means identifying why v6 produces an empty report or documenting the missing information needed to isolate it; no repository file or test is named.
Written by the indexing model from the issue text.
Description
Upgrading from codecov/codecov-action@v5 to v6 causes Codecov to receive an empty report. The CI upload step reports success (exit 0, "Process Upload complete"), but Codecov's processing pipeline records:
Report is empty and cannot be processed
Downgrading back to v5 immediately resolves the issue with no other changes.
- Use
codecov/codecov-action@v5— coverage uploads and processes correctly - Upgrade to
codecov/codecov-action@v6 - CI upload step exits 0 and logs "Process Upload complete"
- Codecov dashboard shows "Unusable report" and breadcrumb trail shows "Report is empty and cannot be processed"
- Dominant language
- No language data
- Stars
- 52
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 codecov/feedback
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePossibly taken @ChiptenIsCool claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 1-2 days Newbie friendliness 42/100
All issues in codecov/feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
janitor-team/janitor#2613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keyxmakerx/Chronicle#2550 ·
Maintainers usually reply within 1 day
-
ci/cd javascript medium sdk
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug good first issue help wanted rust type:infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Open-Glassbeetle/glassbeetle#374 ·
Maintainers usually reply within 1 day