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
Fix Codecov integration #3934
Comments
We're still getting some PRs with coverage reports and some PRs without. |
@hugovk Based on last time I looked at this, the only suggestion I can make is for the authors of all the commits to ensure they've logged into Codecov recently. And click on whatever they want you to click on (if anything). After that, we can at least rule out "developer hasn't logged into Codecov" as a possibility. |
@radarhere Please can you log in to Codecov and see if anything needs clicking? Today's #3964 doesn't have coverage notifications, but it does have coverage on the site: https://codecov.io/gh/python-pillow/Pillow/commit/386002e8923ec9586d4221529963c22f01212ac4 If there's nothing out of the ordinary, let's ask at https://community.codecov.io/. Thanks! |
Reported to Codecov: With a new account there I can frustratingly only post one link in the report, here's the same report with all the links: DescriptionCoverage reports are being created for PRs on Codecov, but most of the time they're not showing as checks the PRs on GitHub. They used to. This makes it hard to see if the PR has tested the changed code. https://codecov.io/gh/python-pillow/Pillow/pulls Here's 5 recent PRs, none have Codecov checks on GitHub:
These mostly show up on the Codecov website itself with coverage:
The most recent to have a Codecov check on GitHub was 8 days ago, but there are older ones without checks: Repositoryhttps://github.com/python-pillow/Pillow Versionscodecov 2.0.15 for Python |
I think this may have resolved itself - every PR for the last three weeks has had code coverage. |
Follow on from #3913 (comment).
Again the Codecov integration isn't reporting on PRs:
#3933
Ping @aclark4life. Perhaps removing and re-adding it may help?
The text was updated successfully, but these errors were encountered: