-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
badge in github not updating #1065
Comments
I think this is a duplicate of #971. I worked around this by using the badge from badges.io instead of the coveralls default. |
We have made some patches to solve some issues we were having with github caching badge resources, please let us know if this is a problem again. |
I'm seeing this issue as well. GitHub Repo shows 0% coverage, while Coveralls Report shows 100% coverage and the embedded badge URL when viewed in browser also shows 100% coverage. I've cleared browser cache, tried multiple browsers, and updated README file, all with no change. |
@thomscode this is a caching issue with github caching the badges. I have reached out them try and get some clarification on how we can solve this issue outside of what their docs say and we are already doing. |
Thanks |
Hi guys. Have the same problem. Any ideas? |
@bytewalls have you managed to fix it ? |
A workaround is just add queryString param to the badge image url, for instance: |
Hi, i also had same problem where my badge shows 45% but on /coveralls.io page actually was 74%. |
This is still broken for me. It's not related to browser cache, AFAICT. I can hand-edit the url all the time, but that's a terrible solution. This isn't broken for other badges, just coveralls... |
Had the same bug, applied the workaround by @moshfeu |
I was having the same problem and found this issue. For me the problem was that the image was cached by github, not my own browser. There is a fix documented here that worked: https://help.github.com/en/articles/about-anonymized-image-urls |
Same problem here. Not related to the browser's cache but to the GitHub's cache. Solved removing the image from Camo's cach, e.g., $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
> {"status": "ok", "id": "216-8675309-1008701"} |
Did not work for me, still facing the same issue |
All solutions listed are not working for me ... |
In my case, by adding
|
This is also an issue for me. Why does github have to cache those badges? |
i solved the same issues with: CTRL + F5 (Chome browser) |
Did you just copy the camo link from the image? |
+1 |
@introkun did you try the solutions above? If you want to share the coveralls URL to your repo I'll check it out for you. |
@afinetooth thanks, the workaround wirked for me. |
@introkun great, glad to hear it. |
According to [#1065](lemurheavy/coveralls-public#1065 (comment))
I think you ha ve more than one action, still not working. I have 2 repos one with one action and it is working and in the one with 3 actions is not working, always shows no status. |
Hi, @HudsonSchumaker. I think you may have been affected by a recent issue with status updates: Can you please open a new issue here, or email us at support@coveralls.io? Share your Coveralls Repo URL and the URLs for any builds that did not receive status updates? We will re-run those for you. The issue should be resolved now, btw, but let us know if you're still experiencing it. We are not 100% sure of its origin or that it won't recur. We are monitoring, but have not seen it happen for at least 12-hours. |
Hi, @afinetooth, |
@HudsonSchumaker great, glad to hear it. |
Main goal was to bypass GitHub URL cache issues on the coverage badge. See: lemurheavy/coveralls-public#1065 Using the opportunity to add a badge regarding supported python versions.
Main goal was to bypass GitHub URL cache issues on the coverage badge. See: lemurheavy/coveralls-public#1065 Using the opportunity to add a badge regarding supported python versions.
Main goal was to bypass GitHub URL cache issues on the coverage badge. See: lemurheavy/coveralls-public#1065 Using the opportunity to add a badge regarding supported python versions, and to exclude GitHub workflows from the source dist (`MANIFEST.in`).
Main goal was to bypass GitHub URL cache issues on the coverage badge. See: lemurheavy/coveralls-public#1065 Using the opportunity to add a badge regarding supported python versions, and to exclude GitHub workflows from the source dist (`MANIFEST.in`).
As coveralls badge seemingly doesn't update as the results change, due to some bug with either coveralls or Github's image caching. lemurheavy/coveralls-public#1065
* Rename s1_lce and s2_lce to s1_correction and s2_correction * Minor change * Update documentation * Update .gitignore * Simplify equality sign * Update to use importlib_resources to suppress warnings * Kill cache of coverage Reference: lemurheavy/coveralls-public#1065 (comment) * Minor change
Badges/image are cached by GitHub. The version number shown on the badge, as a result, wasn't being updated. We use the "query" trick (lemurheavy/coveralls-public#1065 (comment)) to fix it. - Fix bad formatting - Update introductory example; add explanation - Mention "API key"
Badges/image are cached by GitHub. The version number shown on the badge, as a result, wasn't being updated. We use the "query" trick (lemurheavy/coveralls-public#1065 (comment)) to fix it. - Fix bad formatting - Update introductory example; add explanation - Mention "API key"
Badges/image are cached by GitHub. The version number shown on the badge, as a result, wasn't being updated. We use the "query" trick (lemurheavy/coveralls-public#1065 (comment)) to fix it. - Fix bad formatting - Update introductory example; add explanation - Mention "API key"
... i'm not sure where the source of this problem might lay -- browser? github? coveralls?
when I open my repo ( https://github.com/ericblade/mws-advanced ) I see a coveralls badge showing 63. My coverage has never been at 63 on it. When I click the badge, and go to the coveralls page, it shows the badge and coverage stats clearly being 88. If I load the badge SVG directly into my browser, I see 88.
Any ideas? I have tried clearing my cache, using different browsers.. it seems that when I source the image from coveralls, via github, it gives the wrong number, and I don't see how that would be.
The text was updated successfully, but these errors were encountered: