# GitHub comment not appearing

**URL:** <https://community.codecov.com/t/github-comment-not-appearing/4383>\
**Category:** Bug Fixes\
**Created:** [June 28, 2023, 8:34am UTC](https://community.codecov.com/t/github-comment-not-appearing/4383 "2023-06-28T08:34:35Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tpluscode](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tpluscode/32/65_2.png) [@tpluscode](https://community.codecov.com/u/tpluscode)\
**Post date:** [June 28, 2023, 8:34am UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/1 "2023-06-28T08:34:36Z")

</div>

## 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](https://github.com/apps/codecov), if using GitHub  
 I have [validated](https://docs.codecov.com/docs/codecov-yaml#validate-your-repository-yaml) my `codecov.yaml` configuration file.  
 I have filled out the below sections to the best of my ability.  
 I understand that the community boards are a free, best-effort tool. While we hope to have someone on the Codecov team resolve your problem quickly, this is not always possible.

### Description

I sometimes (fairly often) see that the codecov PR comment does not arrive. That is the case with these two PRs in one repo:

> <https://github.com/zazuko/barnard59/pull/119>
>
> I migrated the base package which revealed a dependency cycle between it and \`ba…rnard59-core\`
> 
> Turned out these were only used in e2e tests so I extracted a workspace package for them. May use that soon to finalise the work done in #52

> <https://github.com/zazuko/barnard59/pull/125>

They are not exactly the same, as the latter introduces flags but overall the problem is similar. The branch coverage is correctly loaded and visible at codecov ([branch `base`](https://app.codecov.io/github/zazuko/barnard59/tree/base)). Flags also worked nicely and are [visible](https://app.codecov.io/github/zazuko/barnard59/flags).

However, when I follow the `resultURL` from codecov action, I see uploaded reports but the commits is still “Processing”. Example: [Codecov](https://app.codecov.io/github/zazuko/barnard59/commit/1a7f8c93fe7a3e9c1a671a5a1bc8b3f868e93a64)

### CI/CD URL

Their respective CI runs:

PR #119: [https://github.com/zazuko/barnard59/actions/runs/5343061304?pr=119](https://github.com/zazuko/barnard59/actions/runs/5343061304?pr=119)  
PR #125: [https://github.com/zazuko/barnard59/actions/runs/5390299898?pr=125](https://github.com/zazuko/barnard59/actions/runs/5390299898?pr=125)

### Codecov Output

Example job from PR #125

```auto
==> linux OS detected
https://uploader.codecov.io/latest/linux/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (0c9b79119b0d8dbe7aaf460dc3bd7c3094ceda06e5ae32b0d11a8ff56e2cc5c5 codecov)
==> Running version latest
==> Running version v0.6.1
/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov -n -Q github-action-3.1.4 -F barnard59-sparql
[2023-06-27T13:17:58.459Z] ['info'] 
     _____ _
    / ____ | | |
   | | _____ | | ______  _______
   | | / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |__/ (_| (_) \ V /
    \ _____\___ / \ __,_|\___ |\ ___\___ / \_/

  Codecov report uploader 0.6.1
[2023-06-27T13:17:58.469Z] ['info'] => Project root located at: /home/runner/work/barnard59/barnard59
[2023-06-27T13:17:58.475Z] ['info'] -> Token found by environment variables
[2023-06-27T13:17:58.487Z] ['info'] Searching for coverage files...
[2023-06-27T13:17:58.660Z] ['info'] Warning: Some files located via search were excluded from upload.
[2023-06-27T13:17:58.661Z] ['info'] If Codecov did not locate your files, please review https://docs.codecov.com/docs/supported-report-formats
[2023-06-27T13:17:58.661Z] ['info'] => Found 4 possible coverage files:
  coverage/lcov.info
  coverage/tmp/coverage-1795-1687871876107-0.json
  coverage/tmp/coverage-1802-1687871876059-0.json
  coverage/tmp/coverage-1814-1687871875969-0.json
[2023-06-27T13:17:58.661Z] ['info'] Processing /home/runner/work/barnard59/barnard59/coverage/lcov.info...
[2023-06-27T13:17:58.663Z] ['info'] Processing /home/runner/work/barnard59/barnard59/coverage/tmp/coverage-1795-1687871876107-0.json...
[2023-06-27T13:17:58.665Z] ['info'] Processing /home/runner/work/barnard59/barnard59/coverage/tmp/coverage-1802-1687871876059-0.json...
[2023-06-27T13:17:58.670Z] ['info'] Processing /home/runner/work/barnard59/barnard59/coverage/tmp/coverage-1814-1687871875969-0.json...
[2023-06-27T13:17:58.755Z] ['info'] Detected GitHub Actions as the CI provider.
[2023-06-27T13:17:58.901Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.6.1&token= ******* &branch=separate-coverage&build=5390299898&build_url=https%3A%2F%2Fgithub.com%2Fzazuko%2Fbarnard59%2Factions%2Fruns%2F5390299898&commit=5f23479fe1287ad3a631538167657283b58b3c73&job=CI&pr=&service=github-actions&slug=zazuko%2Fbarnard59&name=&tag=&flags=barnard59-sparql&parent=
[2023-06-27T13:17:59.069Z] ['info'] https://app.codecov.io/github/zazuko/barnard59/commit/5f23479fe1287ad3a631538167657283b58b3c73
https://storage.googleapis.com/codecov/v4/raw/2023-06-27/06251E63E25FA1F536411D504F62083A/5f23479fe1287ad3a631538167657283b58b3c73/489fb567-65d0-4f32-9913-bb1c797dda39.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EJOGFN2JQ4OCTGA2MU5AEIT7OT5Z7HTFOAN2SPG4NWSN2UJYOY5U6LZQ%2F20230627%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20230627T131759Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=a3fa55a9f662f623f26261303844cc5f183153a5caed7f856fee0ad58acbdd15
[2023-06-27T13:17:59.070Z] ['info'] Uploading...
[2023-06-27T13:17:59.237Z] ['info'] {"status":"success","resultURL":"https://app.codecov.io/github/zazuko/barnard59/commit/5f23479fe1287ad3a631538167657283b58b3c73"}

```

### Expected Results

Comment should appear on github

### Actual Results

There is no codecov comment

### Additional Information

It did work previously in that same repo: [Migrate core package by tpluscode · Pull Request #107 · zazuko/barnard59 · GitHub](https://github.com/zazuko/barnard59/pull/107#issuecomment-1598604072)

---

<div class="post-metadata">

**Author:** ![tom](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tom/32/8_2.png) [@tom](https://community.codecov.com/u/tom)\
**Post date:** [July 23, 2023, 11:52pm UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/2 "2023-07-23T23:52:30Z")

</div>

@tpluscode sorry for the delay here. I didn’t get a chance to take a look at this when our logs were still available, so I can’t figure out a concrete reason why the PR comment didn’t send. I do see that the status is `processing` on our end, and I wonder if something happened then to prevent it from moving to a `success`/`failure` state.

If you create another PR, would you expect to see this happen again? Are you able to create something?

---

<div class="post-metadata">

**Author:** ![tpluscode](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tpluscode/32/65_2.png) [@tpluscode](https://community.codecov.com/u/tpluscode)\
**Post date:** [July 24, 2023, 8:40am UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/3 "2023-07-24T08:40:27Z")

</div>

Hi. Thanks for coming back to me about this.  
It’s not the first I’ve seen similar occurrences, in this and other repos. It then always goes away later. This time too, subsequent prs were processed successfully…

---

<div class="post-metadata">

**Author:** ![tom](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tom/32/8_2.png) [@tom](https://community.codecov.com/u/tom)\
**Post date:** [July 24, 2023, 11:29pm UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/4 "2023-07-24T23:29:30Z")

</div>

@tpluscode I see, I think we need to do a better job at clearing our processing queue. I’ll let the product team know and see if we can make improvements here in the next quarter.

Aside from that, are you still running into issues?

---

<div class="post-metadata">

**Author:** ![tpluscode](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tpluscode/32/65_2.png) [@tpluscode](https://community.codecov.com/u/tpluscode)\
**Post date:** [July 25, 2023, 7:25am UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/5 "2023-07-25T07:25:27Z")

</div>

All good, that issue notwithstanding. Thanks

---

<div class="post-metadata">

**Author:** ![tpluscode](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tpluscode/32/65_2.png) [@tpluscode](https://community.codecov.com/u/tpluscode)\
**Post date:** [July 25, 2023, 7:45am UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/6 "2023-07-25T07:45:11Z")

</div>

Ah, interestingly, I may just have triggered that same behavior:

> **[Code coverage done right.](https://app.codecov.io/github/zazuko/barnard59/commit/3a65c8f2b8b84cf68cc0faf23aa3b8d6659c5451)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

> <https://github.com/zazuko/barnard59/actions/runs/5653941693/job/15316015624>

---

<div class="post-metadata">

**Author:** ![tom](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tom/32/8_2.png) [@tom](https://community.codecov.com/u/tom)\
**Post date:** [July 25, 2023, 2:49pm UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/7 "2023-07-25T14:49:27Z")

</div>

@tpluscode hmm, I see a rate-limit error in our logs for that commit. If you do have the [Codecov GitHub app](https://github.com/apps/codecov) installed, can you try uninstalling and reinstalling it?

---

<div class="post-metadata">

**Author:** ![tpluscode](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tpluscode/32/65_2.png) [@tpluscode](https://community.codecov.com/u/tpluscode)\
**Post date:** [July 25, 2023, 3:15pm UTC](https://community.codecov.com/t/github-comment-not-appearing/4383/8 "2023-07-25T15:15:03Z")

</div>

Yea, having pushed some more commits to that same branch a little later, the comment eventually did arrive.

Will try reinstalling the app
