codacy / codacy-coverage-reporter-action

GitHub Action for the codacy-coverage-reporter
Other
56 stars 15 forks source link

[CY-4882] sha512sum: WARNING: 1 computed checksum did NOT match #51

Closed nallwhy closed 2 years ago

nallwhy commented 2 years ago

How can I fix it?

 curl -Ls https://raw.githubusercontent.com/codacy/codacy-coverage-reporter/master/get.sh
     ______          __
    / ____/___  ____/ /___ ________  __
   / /   / __ \/ __  / __ `/ ___/ / / /
  / /___/ /_/ / /_/ / /_/ / /__/ /_/ /
  \____/\____/\__,_/\__,_/\___/\__, /
                              /____/

  Codacy Coverage Reporter

#=#=#                                                                         

######################################################################## 100.0%
 --> Downloading the codacy reporter codacy-coverage-reporter-linux... (13.1.4)
~/.cache/codacy/coverage-reporter/13.1.4 ~/work/momenti-elixir/momenti-elixir
#=#=#                                                                         

#                                                                          1.9%
###################                                                       26.5%
######################################                                    53.9%
############################################################              84.0%
######################################################################## 100.0%
 --> Checking checksum...
#=#=#                                                                         

######################################################################## 100.0%
######################################################################## 100.0%
sha512sum: WARNING: 1 computed checksum did NOT match
codacy-coverage-reporter-linux: FAILED
github-actions[bot] commented 2 years ago

Internal ticket created : CY-4882

dougal commented 2 years ago

Same issue here. As we are not 100% dependent on Codacy action for release, we have ignored failures on it as a temporary workaround.

continue-on-error: true
machadoit commented 2 years ago

@nallwhy @dougal we had a problem with version 13.1.4 but everything should be working now with new versions