codecov-action
codecov-action copied to clipboard
v2: Codecov: Uploader shasum does not match
I've been getting this issue on a few repos lately, and it fails the job. Other jobs in the build pass.
For example:
Run codecov/codecov-action@v2
==> macos OS detected
uploader.codecov.io/latest/macos/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
Error: Codecov: Uploader shasum does not match -- uploader hash: 2c85aba3ee4ee37de3192225f08f25d6be40b43f8a1fab7c4e539babd5e5627b codecov, public hash: 746bca9d7fbbcf95d18c7c5ab713b5d4d857dbdb9fa95e9e0d13f4ee0a91509a codecov
https://github.com/hugovk/humanize/runs/4322709573?check_suite_focus=true
Restarting the build passes, but it's annoying to get the failure and having to restart many jobs to get it green.
We have the same problem: E.g.
Run codecov/[email protected]
with:
...
env:
...
==> linux OS detected
https://uploader.codecov.io/latest/linux/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
Error: Codecov: Uploader shasum does not match -- uploader hash: 48242d3695f4c7dc4c413caedb16c44dd4095e732a6c2a0bd00c173e656feda3 codecov, public hash: 4a19a16d3e3ec6966b3499bb166e08fa2226e64acc68edd97060631b01cf3ee3 codecov
Investigation showed, that the download of https://uploader.codecov.io/latest/linux/codecov will be stopped by the web server after 60 seconds which, does not lead to an error but just an incomplete download.
Sorry that I never responded here, but this, I believe is no longer relevant.
Just saw this:
[code / verify (ubuntu-latest, 16)](https://github.com/mocktomata/mocktomata/actions/runs/4206742475/jobs/7300632624#step:9:9)
Codecov: Uploader shasum does not match -- uploader hash: dcaddc691f835ba8ede36543aa97d934697df3c40a24d15f8c2419550562cc85 codecov, public hash: 080b43eaec3434326bb0f61653a82d27aba15c311ddde9d3f68cb364314f7aae codecov
https://github.com/mocktomata/mocktomata/actions/runs/4206742475
Thanks @unional, taking a look now
btw, just in case I re-update the codecov token in the repo's setting.
@unional looks like it's just a cache thing on our side. The first shasum matches our 0.3.4, while the second one matches 0.3.5. I have gone ahead and requested our cache be cleared, but let me know if you see the issue again
Sure. thx. The newer builds seems to be working.