codecov / codecov/codecov-action

[BUG] Misleading warnings is logged about - Some files were not found --- {"not_found_files": ["**/coverage.xml"]}

Open
#1,862 1 comment 0 reactions 1 assignee View on GitHub

@thomasrockhu-codecov is already working on this.

Since Aug 20, 2025.

[Product] Report Upload [Source] Open Source [Type] Fix bug Codecov Active Support
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

Describe the bug

There is a clear bug that logs a warning like below when it clearly does not have any reasons:

Run codecov/codecov-action@v5.4.3
...
warning - 2025-08-18 10:55:36,838 -- Some files were not found --- {"not_found_files": ["**/coverage.xml"]}
info - 2025-08-18 10:55:36,839 -- Found 1 coverage files to report
info - 2025-08-18 10:55:36,839 -- > /home/runner/work/team-devtools/team-devtools/.tox/py313/coverage.xml
info - 2025-08-18 10:55:37,182 -- Your upload is now processing. When finished, results will be available at: 

To Reproduce

Just use a glob pattern in files.

Expected behavior

No warning logged when glob pattern has matches.

Regression
State whether this is a regression and when the last successful instance occurred

Screenshots
If applicable, add screenshots to help explain your problem.

https://github.com/ansible/team-devtools/actions/runs/17038322115/job/48295921968?pr=313#step:18:314

Product Area
If applicable, the product with the given bug (e.g. coverage, test analytics, browser extension, bundle analysis)

Versions

  • OS: [e.g. linux, ubuntu@v24, macos arm64, windows]
  • Git Host: [e.g. GitHub, GitLab, Bitbucket]
  • CI/CD: [e.g. GitHub Actions, CircleCI]
  • Uploader: [e.g. codecov-action@v5.3.1, codecov-circleci-orb@v5.2.0, codecov-cli@v10.0.1, uploader@v0.8.0]

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

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

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.