codecov-action: codecov fails in github actions
backgrond
-
my setup for codecov has worked well so far
- you can regular updates with each pr commits here
- I haven’t change my repo settings
-
as I’ve inadvertently pushed a folder that I wasn’t supposed to, then I merged a pr to remove said folder
-
here is my codecov.yml
issue
- on the aforementioned last pr linked above the github action ci complained with the log below
_____ _
/ ____| | |
| | ___ __| | ___ ___ _____ __
| | / _ \ / _` |/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| | __/ (_| (_) \ V /
\_____\___/ \__,_|\___|\___\___/ \_/
Bash-1.0.3
==> git version 2.31.1 found
==> curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
==> GitHub Actions detected.
Env vars used:
-> GITHUB_ACTIONS: true
-> GITHUB_HEAD_REF: remove-speedtest
-> GITHUB_REF: refs/pull/136/merge
-> GITHUB_REPOSITORY: iapicca/yak_packages
-> GITHUB_RUN_ID: {{I'll keep this for myself}}
-> GITHUB_SHA: {{I'll keep this for myself}}
-> GITHUB_WORKFLOW: CI
-> Issue detecting commit SHA. Please run actions/checkout with fetch-depth > 1 or set to 0
project root: .
Yaml found at: codecov.yml
==> Running gcov in . (disable via -X gcov)
==> Python coveragepy not found
==> Searching for coverage reports in:
+ .
-> Found 7 reports
==> Detecting git/mercurial file structure
==> Reading reports
+ ./packages/yak_tween/coverage/lcov.info bytes=2228
+ ./packages/yak_utils/coverage.lcov bytes=687
+ ./packages/yak_test/coverage.lcov bytes=339
+ ./packages/stub/coverage.lcov bytes=678
+ ./packages/yak_runner/coverage.lcov bytes=6429
+ ./packages/yak_widgets/coverage/lcov.info bytes=1444
+ ./packages/yak_error_handler/coverage.lcov bytes=1017
==> Appending adjustments
https://docs.codecov.io/docs/fixing-reports
+ Found adjustments
==> Gzipping contents
8.0K /tmp/codecov.yP3SSF.gz
==> Uploading reports
url: https://codecov.io
query: branch=remove-speedtest&commit={{I'll keep this for myself}}
&build={{I'll keep this for myself}}&build_url=http%3A%2F%2Fgithub.com%2Fiapicca%2Fyak_packages%2Factions%2Fruns%2F911981303&name=&tag=&slug=iapicca%2Fyak_packages&service=github-actions&flags=&pr=136&job=CI&cmd_args=
-> Pinging Codecov
https://codecov.io/upload/v4?package=bash-1.0.3&token=secret&branch=remove-speedtest&commit={{I'll keep this for myself}}&build={{I'll keep this for myself}}&build_url=http%3A%2F%2Fgithub.com%2Fiapicca%2Fyak_packages%2Factions%2Fruns%2F911981303&name=&tag=&slug=iapicca%2Fyak_packages&service=github-actions&flags=&pr=136&job=CI&cmd_args=
{'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
404
==> Uploading to Codecov
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 5026 100 171 100 4855 1000 28391 --:--:-- --:--:-- --:--:-- 29220
100 5026 100 171 100 4855 1000 28391 --:--:-- --:--:-- --:--:-- 29220
{'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
- the suggested fix is quite obscure to me
{'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
request
as I don’t really want to run anything locally can someone help me to fix the issue inside the CI
thank you
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 48
- Comments: 30 (13 by maintainers)
Commits related to this issue
- [CI] Configure Codecov action to use token This is a workaround for https://github.com/codecov/codecov-action/issues/330 — committed to vividus-framework/vividus by valfirst 3 years ago
- [CI] Configure Codecov action to use token (#1698) This is a workaround for https://github.com/codecov/codecov-action/issues/330 — committed to vividus-framework/vividus by valfirst 3 years ago
- temporarily disable codecov fail on error. see https://github.com/codecov/codecov-action/issues/330 — committed to FigureTechnologies/ats-smart-contract by ktalley-figure 3 years ago
- :green_heart: Temporarily prohibit Codecov upload failures from failing CI To address recently flaky Codecov upload jobs failing CI. - see: codecov/codecov-action/issues/330 — committed to TeoZosa/cookiecutter-cruft-poetry-tox-pre-commit-ci-cd by TeoZosa 3 years ago
- :green_heart: Temporarily prohibit Codecov upload failures from failing CI To address recently flaky Codecov upload jobs failing CI. - see: codecov/codecov-action/issues/330 — committed to TeoZosa/structlog-sentry-logger by TeoZosa 3 years ago
- :green_heart: Temporarily prohibit Codecov upload failures from failing CI To address recently flaky Codecov upload jobs failing CI. - see: codecov/codecov-action/issues/330 Original-Commit: TeoZosa... — committed to TeoZosa/cookiecutter-cruft-poetry-tox-pre-commit-ci-cd-instance by TeoZosa 3 years ago
- Use codecov token This fixes issue https://github.com/codecov/codecov-action/issues/330 — committed to nrmnrsh/nrmnrsh.com by schorfES 3 years ago
- [CI] Remove workaround for Codecov action issue codecov/codecov-action#330 — committed to vividus-framework/vividus by valfirst 3 years ago
- [CI] Remove workaround for Codecov action issue (#1702) codecov/codecov-action#330 — committed to vividus-framework/vividus by valfirst 3 years ago
- :green_heart: Re-enable CI failure on Codecov upload failures see: codecov/codecov-action/issues/330 Signed-off-by: Teo Zosa <teofilo@sonosim.com> — committed to TeoZosa/cookiecutter-cruft-poetry-tox-pre-commit-ci-cd by TeoZosa 3 years ago
- :green_heart: Re-enable CI failure on Codecov upload failures see: codecov/codecov-action/issues/330 Signed-off-by: Teo Zosa <teofilo@sonosim.com> Original-Commit: TeoZosa/cookiecutter-cruft-poetry-... — committed to TeoZosa/cookiecutter-cruft-poetry-tox-pre-commit-ci-cd-instance by TeoZosa 3 years ago
- :green_heart: Re-enable CI failure on Codecov upload failures see: codecov/codecov-action/issues/330 — committed to TeoZosa/structlog-sentry-logger by TeoZosa 3 years ago
- :green_heart: Re-enable CI failure on Codecov upload failures see: codecov/codecov-action/issues/330 — committed to TeoZosa/structlog-sentry-logger by TeoZosa 3 years ago
- :green_heart: Re-enable CI failure on Codecov upload failures see: codecov/codecov-action/issues/330 — committed to TeoZosa/structlog-sentry-logger by TeoZosa 3 years ago
Uploads are failing sporadically across all of my public repositories (so no token should be required, but same error message). A couple of examples:
Started over the weekend.
Got it, looks like there is another issue. Our product team is looking into it, and I’ll update here as soon as I have any news. Thanks for your patience everyone.
We have also seen the same thing in evalml:
https://github.com/alteryx/evalml/pull/2256/checks?check_run_id=2766309621 https://github.com/alteryx/evalml/actions/runs/915203323 https://github.com/alteryx/evalml/runs/2764848236?check_suite_focus=true
Is there a plan for a fix from codecov? Any help would be appreciated! This started happening for us sometime today.
Hi all, I have deployed
1.5.2
which should fix the above issue. I will continue to keep this open at least for the next 24 hours unless there are other issues.v1.5.2 seems to have fixed my problem. Thank you!
As a sidenote, we released
v1.5.1
which contains the latest version of the bash uploader1.0.3
(as well as dependency updates and small fixes). I don’t expect this to resolve the underlying issue but just wanted everyone to be aware of the change.@thomasrockhu Seems to be working now. Thanks for the quick fix!
+1
We are seeing this issue in pycalphad where sometimes the uploads are successful and other times they are not, with no changes in our configuration. We have broken out the upload step for our different platforms into a different job within the GitHub Action, so we can confirm that it’s isolated here.
We use the GitHub token, so rotating tokens as suggested in the SO question doesn’t really apply.
Sorry about that, I’ve opened a PR and I look to deploy in the next hour.
This repo has version 1.0.2 of the bash uploader, but the latest one is 1.0.3. They’ve updated how an HTTP response is checked, so I’m guessing that’s where we run into issues.
Using my own version of the codecov-action (with bash uploader 1.0.3, see #336), uploading seems to work again. For the time being, a workaround is to just use the bash uploader directly, for example like so: https://github.com/SpoonLabs/sorald/pull/560/files
Everything was fine before. Today I am experiencing this issue for my public repos. As far I know, public repos don’t require a token.
One related side question.
My GitHub notifications are configured to notify me only when an action fails. I have configured codecov action to not fail ci on error of codecov.
So, my ci will not fail. but I still want to get notified when upload to codecov fails, or any codecov issue occurs inside the gh action run. Is that possible?