Description recently we had experiences an issue with codecov’s status stuck at expecting results. [59] We found it might be related to a failed upload ==> Circle CI detected. project root: . → token set from env Yaml found at: .codecov.yml ==> Running gcov in . (disable via -X gcov) ==> P…

Would you try using checkout@v1 for your action? We have seen this issue here , and I want to make sure this isn’t the reason you’re not getting a status check back. edit: we do not recommend using checkout@v1 over checkout@v2

Any updates on this one? We are still having this problem with all our builds. :cry: E.g. here: Change how to count records in RobotsTxtListener by fritzmg · Pull Request #1590 · contao/contao · GitHub

Hi! We have this exact same problem. Neither re-running the pipeline fixes this issue. We’re currenlty with a couple PRs open beause of this. It’s a private project and it belongs to a paid codecov.io organization. Anyone from support team could take a look and help us debug this issue? I can giv…

@drazisil Is this thread still active or should I open a new one?

This is happening on our oss project again (last time was August 2019). Can we get an update please? I have already tried pushing new commits to kick it off again but still having same problem.

Same issue at getsentry/sentry-php . The status is not a required GitHub status check if it matters for some reason, and for all recent commits I keep seeing the message “Notifications are pending CI completion. Waiting for GitHub’s status webhook to queue notifications.” on Codecov, although the bui…

Hey @stefano93 , @mydiemho , @leofeyer , @igorgcosta ! Thanks for reaching out, sorry for the issue. We believe that this has to do with rate limiting on the Github API (and yes, that means the error message is not very correct): [image] We are in active conversations with Github’s partnerships tea…

@jerrod Thank you for your feedback. We are already using the GitHub App but it is still not working. Let’s wait and see about the API rate limit.

@jerrod I switched to the GitHub App and for one PR it seemed to work fine, but then on a plain new commit I got the error There was an error processing coverage reports. [image] Code coverage done right. Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesom…

Getting this too, it’s really taking up a lot of time trying to get the codecov reports to come back.

An immediate possible workaround is, if you aren’t already is to use the Github App connection vs. an Oauth App/Team Bot: https://github.com/apps/codecov We are using the app already for our organization, and have been getting this issue pretty consistently. The codecov bot replies to all the PR…

Codecov status stuck at "waiting for status to be reported" on github

Support

leofeyer June 11, 2020, 1:15pm 40

Sure, here you go:

Repo: contao/contao
RR: contao/contao#1605
Commit: 778993e2
GitHub Action: 549313476
Codecov commit: f60131bd

Codecov GitHub action sometimes fails to report status despite move to checkout v1

Topic		Replies	Views
GitHub codecov check in pull request suddenly stuck Support github	2	474	July 17, 2020
Codecov status stuck at "waiting for status to be reported" Support	14	2664	November 5, 2019
PRs not registering in codecov/PR status Support	39	1816	January 18, 2021
GitHub bot comment not triggering Bug Fixes	35	3799	April 28, 2020
Codecov does not push back to Github Support github	6	386	February 12, 2021

Codecov status stuck at "waiting for status to be reported" on github

Related topics