Codecov-patch fails on master consinstently

Description

Hello I am experiencing issues with codecov-patch. I have found other issues wanting to turn it of. The thing is I don’t want to turn it off, I just want to figure out why it keeps failing.

Here is an example from the last fail

  • Create pull request from branch X to development
    • Merge X to development
    • push action triggers on development
    • codecov-patch says everything is ok.
  • Merge development to master
    • codecov-patch fails.
    • Click link on failed action (no diff)
    • codecov-patch

The actions for each branch are the same.

The pull request from X branch increased coverage in both development and master and prior to that master and development had the same code (not same history)

Commit SHAs

Master: 35e6abd08a8d162abab353141b0c33721bbb4dc9
Development: 414421791792652e032982255085b164e8f02c54
PR X branch: 7d7d76bffe2eec97a5fbbf15923ba7f080d979f6

Repository

Repo

CI/CD or Build URL

Linux
Windows
MacOS

Uploader

Github actions through workflow (codecov/codecov-action@v2)

Codecov Output

Output is huge for 12 runs but you can find it at the corresponding github actions
Linux
Windows
MacOS

Expected Results

Codecov-patch doesn’t fail

Actual Results

Codecov-patch fails my pipeline

Additional Information

My codecov config

codecov:
  bot: "codecov-io"
  ci:
    - "github.com"
  strict_yaml_branch: "master"
  max_report_age: off
  disable_default_path_fixes: no
  require_ci_to_pass: yes
  notify:
    # This is the number of ci builds from github actions
    # 3 OS x 4 Python Versions = 12
    after_n_builds: 12
    wait_for_ci: yes
coverage:
  precision: 5
  round: down
  range: 90..100
  status:
    project:
      default:
        # Basic
        target: 90%
        threshold: 2%
        flags:
          - unittests
        paths:
          - "calculate_anything/"
        # Advanced
        branches:
          - master
        if_not_found: failure
        only_pulls: false
        if_ci_failed: error

So I think there is some strange behavior on our end that is making this happen @tchar. I have talked to the product team about it, but I think for now, the workaround is to remove

        branches:
          - master

from your codecov.yml. The reason being that the commits to development are coming back as GitHub Checks, while the commits to master are GitHub Statuses. The behavior shouldn’t be different, but it currently is. We do believe Checks are the way moving forward.