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

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

Open
justinvp opened this issue Feb 26, 2025 · 0 comments
Open

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

justinvp opened this issue Feb 26, 2025 · 0 comments
Assignees
Labels
bug Something isn't working Medium Medium Priority Issues (to be fixed or re-evaluated in 3 months

Comments

@justinvp
Copy link

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.

@justinvp justinvp added the bug Something isn't working label Feb 26, 2025
@thomasrockhu-codecov thomasrockhu-codecov self-assigned this Feb 26, 2025
@thomasrockhu-codecov thomasrockhu-codecov added the Medium Medium Priority Issues (to be fixed or re-evaluated in 3 months label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Medium Medium Priority Issues (to be fixed or re-evaluated in 3 months
Projects
None yet
Development

No branches or pull requests

2 participants