Repeat/infinite status check updates and comment edits

Support
1

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.

Description

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.

CI/CD URL

N/A (internal)

Codecov Output

Please provide the full output of running the uploader on your CI/CD. This will typically have the Codecov logo as ASCII.
N/A (internal)

Expected Results

A single status check is posted/reported and a single comment (or edit to original comment) is performed.

Actual Results

See image showing how often Codecov is updating comment in response to status update:

Screen Shot 2022-09-15 at 2.29.44 PM
Screen Shot 2022-09-15 at 2.29.44 PM1974×1478 306 KB

2

@btrautmann can you provide a commit SHA so we can investigate?

3

@tom one of the one’s that’s experienced this was ec980c10e547cec24812306e6de6d48b62584715 on Sep 19.

4

@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?

5

@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?

6

@btrautmann no worries, I’ll see what the product team needs specifically. Thanks for getting back to me.

7

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.

8

Got it, I’ll get back to you as soon as I can figure out what’s happening @btrautmann

9

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.

10

@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.

11

@btrautmann ok, we’ve made some fixes on our end for this. I know it’s been awhile, but would you be able to ping back if you see any weirdness with notifications?

12

Thanks for looping back @tom . We made some changes on our end to work around these issues, but another team implemented them so I’m not familiar with the changes. I can certainly let you know if we see any issues in the future, but in the meantime we can probably consider this ticket closed!

1 Like