codecov / codecov/codecov-action

[BUG] No "codecov/project" check is run although configured

Open
#1,802 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Source] Support [Type] Investigation bug codecov/codecov-action
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

Describe the bug

I have the following .codecov.yml which seems to be properly configured to enable both project and patch checks. But neither in master branch nor pull requests I don't see codecov/project checks run.

Could you please tell if it's a bug or misconfiguration? Thanks a lot.

Environment (please complete the following information):

I have a matrix strategy set up with different OS and compilers.

For distinguishing between different configuration I use flags. That's how Codecov job is set up for each runner:

    - name: Upload coverage reports to Codecov (Linux, MacOS)
      if: runner.os != 'Windows'
      uses: codecov/codecov-action@v5
      with:
        token: ${{ secrets.CODECOV_TOKEN }}
        flags: ${{ matrix.os }}-${{ matrix.c_compiler }}-${{ matrix.format_lib }}
        directory: ${{ steps.strings.outputs.build-output-dir }}/coverage
        fail_ci_if_error: true

And finally I manually trigger notifications because those jobs are run in parallel and for some flags there's no coverage (e.g. Windows):

    - name: Trigger notifications for Codecov
      if: ${{ !cancelled() }}
      uses: codecov/codecov-action@v5
      with:
        token: ${{ secrets.CODECOV_TOKEN }}
        run_command: send-notifications
        fail_ci_if_error: true

Here's a link to a full workflow file.

Expected behavior

Both codecov/project and codecov/patch checks are run.

Screenshots

Image

Additional Information

I've already reset the repo and reinstalled the Codecov app, but it didn't help

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.

Research direction

Start by reading .codecov.yml and .github/workflows/cmake-multi-platform.yml, then inspect the linked example PR and the two Codecov action invocations. Determine whether the workflow configuration should produce codecov/project and codecov/patch checks; done means identifying a reproducible configuration issue or confirming that the behavior is expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, yaml
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.