[CY-6444] 13:10:10 breaks on Heroku CI

[jeremiemv]

trafficstars

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

Running reporter on Heroku CI Linux 1f5dffb8-3a19-494f-9817-d239e02259df 4.4.0-1104-aws #109-Ubuntu SMP Tue May 10 11:27:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Expected Behavior

We use bash <(curl -Ls https://coverage.codacy.com/get.sh) to report after running our test suite.

Actual Behavior

~ $  bash <(curl -Ls https://coverage.codacy.com/get.sh)
     ______          __
    / ____/___  ____/ /___ ________  __
   / /   / __ \/ __  / __ `/ ___/ / / /
  / /___/ /_/ / /_/ / /_/ / /__/ /_/ /
  \____/\____/\__,_/\__,_/\___/\__, /
                              /____/

  Codacy Coverage Reporter

######################################################################### 100.0%
 --> Downloading the codacy reporter codacy-coverage-reporter-linux... (13.10.10)
######################################################################### 100.0%
 --> Checking checksum...
######################################################################### 100.0%
 --> Expected checksum
f34766e82839a9847d4d8bf80028e61c1225528a803b115591837d41cb09c4913326263890c669ce1a45a20614cddf668ea9d6fe2a7475716d638cd430c10f42  codacy-coverage-reporter-linux
 --> Actual checksum
f34766e82839a9847d4d8bf80028e61c1225528a803b115591837d41cb09c4913326263890c669ce1a45a20614cddf668ea9d6fe2a7475716d638cd430c10f42  codacy-coverage-reporter-linux
codacy-coverage-reporter-linux: OK
/dev/fd/63: line 218:  3170 Killed                  /app/.cache/codacy/coverage-reporter/13.10.10/codacy-coverage-reporter "report"

 --> Failed!

But when using 13.10.8, it works again

~ $ export CODACY_REPORTER_VERSION=13.10.8
~ $ bash <(curl -Ls https://coverage.codacy.com/get.sh) report --help
     ______          __
    / ____/___  ____/ /___ ________  __
   / /   / __ \/ __  / __ `/ ___/ / / /
  / /___/ /_/ / /_/ / /_/ / /__/ /_/ /
  \____/\____/\__,_/\__,_/\___/\__, /
                              /____/

  Codacy Coverage Reporter

 --> Downloading the codacy reporter codacy-coverage-reporter-linux... (13.10.8)
######################################################################### 100.0%
 --> Checking checksum...
######################################################################### 100.0%
 --> Expected checksum
304765c54daee2a8cca3ec2d5d0524525623c66a9667e49eb907d6bfd37e7f69dd9c15763b250d4dc8c6bc080582957d79d59276309ce50260f04e33240823d4  codacy-coverage-reporter-linux
 --> Actual checksum
304765c54daee2a8cca3ec2d5d0524525623c66a9667e49eb907d6bfd37e7f69dd9c15763b250d4dc8c6bc080582957d79d59276309ce50260f04e33240823d4  codacy-coverage-reporter-linux
codacy-coverage-reporter-linux: OK
Command: report
Usage: codacy-coverage-reporter report
  --project-token | -t  <your project API token>
  --api-token | -a  <your account api token>
  --organization-provider  <organization provider>
  --username | -u  <your username>
  --project-name | -p  <project name>
  --codacy-api-base-url  <the base URL for the Codacy API>
  --commit-uuid  <your commit SHA-1 hash>
  --http-timeout  <Sets a specified read timeout value, in milliseconds, to be used when interacting with Codacy API. By default, the value is 10 seconds>
  --sleep-time  <Sets a specified time, in milliseconds, to be used when waiting between retries. By default, the value is 10 seconds>
  --num-retries  <Sets a number of retries in case of failure. By default, the value is 3 times>
  --skip | -s  <skip if token isn't defined>
  --language | -l  <language associated with your coverage report>
  --coverage-reports | -r  <your project coverage file name>
  --partial  <if the report is partial>
  --prefix  <the project path prefix>
  --force-coverage-parser  <your coverage parser>
        Available parsers are: opencover,clover,lcov,phpunit,go,jacoco,dotcover,cobertura


 --> Succeeded!

.

[github-actions[bot]]

Internal ticket created : CY-6444

[jeremiemv]

Hi. Any idea when this will be picked up?

[jeremiemv]

Hello hello?

[DMarinhoCodacy]

Hello @jeremiemv! Sorry for this huge delay. In meantime, we bumped the version to 13.13.0 and I had the confirmation you already tried this version and it worked. Thanks for contacting us.