Before submitting a topic, please confirm the following
I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my
codecov.yaml configuration file.
I have filled out the below sections to the best of my ability.
We’re seeing repeat/infinite status check updates (and as a result, codecov report comment edits) on our PRs which is causing us to hit the limit for status check updates on a given SHA for a PR (this limit, per Github, is 1000/SHA). This is a pretty big blocker as it prevents us from merging a PR that has run Codecov.
Please provide the full output of running the uploader on your CI/CD. This will typically have the Codecov logo as ASCII.
A single status check is posted/reported and a single comment (or edit to original comment) is performed.
See image showing how often Codecov is updating comment in response to status update:
@btrautmann can you provide a commit SHA so we can investigate?
@tom one of the one’s that’s experienced this was
ec980c10e547cec24812306e6de6d48b62584715 on Sep 19.
@btrautmann woof, ok I see that we are sending a lot of notifications here. Is there anything particular or out of the ordinary in your CI setup? Would you be able to share the Codecov logs from CI?
@tom the only thing I’d say is maybe atypical is that we use Policy Bot to aid in approvals and PR audits. This runs when certain things occur on a PR to validate whether a specific flow chart of requirements has been met. I don’t see how this would interfere/cause Codecov to do weird things, though.
I’m not sure I should share logs publicly. Is there a more secure/less public channel we could use to communicate/transfer those?
@btrautmann no worries, I’ll see what the product team needs specifically. Thanks for getting back to me.
Thank you. We’ve had to disable Codecov on our repository until this is resolved, so we’d super appreciate any escalation we can get on this. Thank you.
Got it, I’ll get back to you as soon as I can figure out what’s happening @btrautmann
Hi, has there been any movement on this? We’ve implemented some workarounds on our end via PolicyBot to mitigate how often we run into this but it’s still happening occasionally.
@btrautmann there isn’t any new update here, but it’s in our engineering team’s hands. I’m sorry, I pinged them back about this to see if we can prioritize it higher.