search

lemurheavy / coveralls-public

The public issue tracker for coveralls.io
http://coveralls.io
124 stars 7 forks source link

coveralls link doesn't show up under github pull requests #1683

Open shree6666 opened 1 year ago

shree6666 commented 1 year ago

Under github pull requests, coveralls links showing increased or decreased coverage, magically disappeared starting 1st Dec 2022. We made sure every setting we could find in place. Is there a bug reported already about this? Please assist what settings can we check in order to fix the issue.

image

afinetooth commented 1 year ago

Hi @shree6666 sorry for the delay here. I'm not aware of such an issue and am not seeing it in any repos we monitor. Can you share your Coveralls Repo URL so we can look into it further for you? If your repo is private or sensitive in any way, you can send to support@coveralls.io. Thanks.

shree6666 commented 1 year ago

I will send an email if there can be a post mortem since this issue is already fixed. We had to delete & re-add our repo to coveralls & coverage started showing up again under github pull requests (no legacy code updated for making it work). Unfortunately, as a side effect of above, we lost coveralls history (recovery would be nice to have). For the period from Dec 1, 2022 through Feb 28, 2023, we had no coverage showing up. Please let me know.

afinetooth commented 1 year ago

@shree6666 apologies for the late reply, and I'm sorry it happened that you lost you coverage history on your repo. As an offer in apology, we have applied a one month free service credit to the account of the subscription for the private Github org you are a member of (if you'd like more details on that, please email us at support@coveralls.io and mention this issue).

I happened to come across your original post about this issue on StackOverflow (which references this post), and from that description realized you were experiencing this issue now listed in the Common Issues & Troubleshooting section of our (updated) docs.

As the root cause of your issue is probably a problem with the OAuth token of your repo owner, you might be interested in joining the beta for our new Github integration, which is based on a Github App and avoids the need to leverage user tokens for common actions like sending status updates.

The new integration is very stable and we will add you to a dedicated support channel in our Slack workspace to provide quick support for any problems you may have migrating your org to the new integration.

Last thought: If you belong to any org with a paid subscription to Coveralls, you can send issues to support@coveralls.io, which will get a quicker response. This board is a community issues board where, we hope, other users will assist open source users of Coveralls, but we try to seep the board as often as we can, which is more often these days.