codecov / codecov/codecov-cli

[BUG] Regression finding coverage files to report in v10.1.0

Open
#651 0 comments 0 reactions 1 assignee View on GitHub

@thomasrockhu-codecov is already working on this.

Since Feb 26, 2025.

bug codecov/codecov-cli Medium
Dominant language
Python
Stars
89
Forks
64
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

We upload coverage from a GitHub Actions workflow:

      - name: Upload code coverage
        uses: codecov/codecov-action@v4
        with:
          directory: coverage/
          files: "*,!.gitkeep"
          fail_ci_if_error: false
          verbose: true
          token: ${{ secrets.CODECOV_TOKEN }}

We haven't made any configuration changes on our end, but we started seeing a significant drop in coverage in Codecov which coincided with the v10.1.0 release of the Codecov CLI.

Looking at the CI logs, when v10.0.1 of the Codecov CLI is used, it found 79 coverage files to report. With v10.1.0, it only finds 4 coverage files to report.

Expected behavior
To continue finding the same amount of coverage files to report

Regression
Yes. The last successful run that found all 79 files was Feb 18, 2025 at 3:27 PM PST. The next run that found only 4 files was at Feb 19, 2025 at 10:43 AM PST.

Product Area
coverage

Versions

  • OS: ubuntu@v22
  • Git Host: GitHub
  • CI/CD: GitHub Actions
  • Uploader: codecov-action@v4

Commit and CI link
Provide the commit SHA and CI link. If applicable, provide the entire Codecov output from CI.

Example of success: 79 files found, using v10.0.1:

Next commit that fails: only 4 files found, using v10.1.0:

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.