-
Notifications
You must be signed in to change notification settings - Fork 213
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
unable to upload coverage report #43
Comments
Is this from a PR? Is the source of the PR the same repo as the target or is it a fork? |
I have the exact same issue. In my case it's no PR, just a push. Edit: just updated the action from v1.0.3 to v1.0.5 and it works. |
Hi @liaogz82! Thank you for bringing this up. Just want to make sure that there weren't any obvious errors in your setup:
Let me know if you still encounter any problems after addressing those two things so we can punch in a support ticket |
Let me try the |
Any luck @liaogz82? If not, please submit a support ticket here and we'll help you to get up and running as quickly as possible: https://codecov.io/support |
This is still a problem for HTTP 400
Please provide the repository token to upload reports via `-t :repository-token` This is from the correct repo-owner and with correctly set-up secrets token. |
But maybe this is indeed different from the original issue raised here? I will open another issue. |
Hi all, we apologize for the timeouts and delays. This is a problem we've identified at Codecov and are actively trying to fix. |
@CasperWA Is your build being triggered for a pull request from a fork? If so that error is expected since GH doesn't make secrets available to runners in that particular case.
Here's the related discussion https://github.saobby.my.eu.orgmunity/t5/GitHub-Actions/Make-secrets-available-to-builds-of-forks/td-p/30678 |
It is. I also commented on it in the other issue #44 I opened.
This makes sense for me from a security point-of-view, since if one was able to access secrets from another user, one could retrieve them. Think for example of a case, where I create an Action that prints all secrets, or tries to go through commonly names secrets. I then make a PR against any repository and it would then provide me with the secrets of the external owner's repository - not good. In the context of codecov, the solution would be what is done for Travis and other CIs, namely to have token-less, but still "safe", access through the codecov API for uploading coverage reports, but through GitHub Actions. |
Seeing the same issues (using v1.0.5) on the check runs of our repo. It worked maybe once or twice (can't really tell) on a feature branch yesterday to try out your service. Output looks like:
Happens on all matrix jobs for a couple of minutes before it gives up. |
Apparently, there's no easy way to submit coverage reports from GitHub pull request builds without exposing this reporter ID. Coverage diff reports should now come in from pull request builds after this commit. The expectation is that Code Climate will comment on the pull requests and mark the build as failed or succeeded based on the coverage diff. This commit also disables sending code coverage reports to Codecov, which has been broken for a while now: codecov/codecov-action#43
This reverts commit 9cece41. codecov/codecov-action#43 (comment)
I'm also experiencing the same issue, more or less randomly. Using v1.0.5 |
|
Same issue here; a bunch of sleeps and eventually
because of |
Using |
Ok It is working on my side. Thanks |
I'm still experiencing this issue even with Update: On second try, it did work with Another update: Failing again. Here is the public repo for reference: https://github.com/ambianic/ambianic-ui/runs/604157465
|
+1 |
Still experiencing this error as well. It's artificially doubling our build times as we wait for the Codecov upload to complete. |
This error is still present after updating to v1.0.7. Any comments from the codecov team?
The codecov portion of the action script looks like this:
|
Sadly this is also affecting me, although I am on @v1.
|
Encountered this just now. It's consuming GitHub actions minutes with all the failed coverage uploads. Was using v1.0.5 and I tried switching over to using v1.0.7. The same issue.
Any updates on this? |
In our case it turned out to be the choice of name for the Although the codecov error message in the github action log was not helpful, Tom provided a good clue on the codecov forum. Hope it helps others. |
Tried going back to v1.0.5, the issue is still there. All we get now are failed uploads to CodeCov. |
We are seeing this seemingly randomly as well. We are running our build on GitHub Actions but not using the Codecov action directly -- rather, we call the This is incredibly difficult to diagnose, as it could be a networking issue with GitHub Actions, an API reliability issue with Codecov, or any number of other things. Anecdotally, we have seen that these tend to cluster in time (for example we just saw two of them back-to-back), which leads me to suspect it's a Codecov API reliability issue, but this is entirely conjecture. Any suggestions or ideas from the Codecov team would be super appreciated. |
Getting same/similar issue on Appveyor:
https://ci.appveyor.com/project/heldersepu/swashbuckle/builds/34821946 |
Unfortunately, there are a lot of different issues that are happening in this thread making difficult for us to triage and fix. If you are seeing this, please make a ticket in our community boards. |
@thomasrockhu But here is a ticket in the community board: |
* path to coverage XML was incorrect * latest @1.X version must be specified (is not taken by default), see: codecov/codecov-action#43
See also: codecov/codecov-action#258 and codecov/codecov-action#43. Signed-off-by: Tao He <linzhu.ht@alibaba-inc.com>
…ge info." This reverts commit 8fc2352. It seems there is an issue codecov/codecov-action#43 and we should wait to see if it will be resolved. The same setup worked a day ago...
…ge info." This reverts commit 8fc2352. It seems there is an issue codecov/codecov-action#43 and we should wait to see if it will be resolved. The same setup worked a day ago...
Hi, I am unable to upload the coverage report into codecov. Below is the image. Could it be possible that github block internet access?
The text was updated successfully, but these errors were encountered: