tracking: codacy/codacy-coverage-reporter-action#97
The Codacy coverage reporter sometimes fails when sending the final coverage notification:
--> Codacy reporter codacy-coverage-reporter-linux already in cache
Running command: /home/runner/.cache/codacy/coverage-reporter/14.1.3/codacy-coverage-reporter final --project-token *** -->
2026-04-22 19:42:24.313Z info [ConfigurationRules] API base URL: https://api.codacy.com/ - (ConfigurationRules.scala:82)
2026-04-22 19:42:24.314Z info [CommitUUIDProvider] CI/CD provider GitHub Actions found Commit UUID 4ef5bc3eddb7a9f86763bd50bd3a9dc69c7d31fa - (CommitUUIDProvider.scala:135)
2026-04-22 19:42:54.465Z error [CodacyCoverageReporter] Failed to send final coverage notification: Error doing a post to https://api.codacy.com/2.0/commit/4ef5bc3eddb7a9f86763bd50bd3a9dc69c7d31fa/coverageFinal: exhausted retries due to Read timed out - (CodacyCoverageReporter.scala:28)
--> Failed!
Occurrence:
https://github.com/CycloneDX/cyclonedx-python-lib/actions/runs/24752613346/job/72575940666#step:3:418
Workflow definition:
|
- name: Run codacy-coverage-reporter |
|
env: |
|
CODACY_PROJECT_TOKEN: ${{ secrets.CODACY_PROJECT_TOKEN }} |
|
if: ${{ env.CODACY_PROJECT_TOKEN != '' }} ## see https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-secrets |
|
# see https://github.com/codacy/codacy-coverage-reporter-action |
|
uses: codacy/codacy-coverage-reporter-action@89d6c85cfafaec52c72b6c5e8b2878d33104c699 # v1 |
|
with: |
|
project-token: ${{ env.CODACY_PROJECT_TOKEN }} |
|
coverage-reports: ${{ env.REPORTS_DIR }}/coverage/* |
I can only speculate, but this might be related to the large amount of coverage data produced across our test matrix.
It sometimes fails, and sometimes the upload works as expected — for example, this run passed:
https://github.com/CycloneDX/cyclonedx-python-lib/actions/runs/24696612747/job/72230869738#step:3:420
tracking: codacy/codacy-coverage-reporter-action#97