codacy-coverage-reporter-action icon indicating copy to clipboard operation
codacy-coverage-reporter-action copied to clipboard

[TCE-1015] Coverage generates but action cannot properly send back to Codacy

Open cougrimes opened this issue 8 months ago • 1 comments

I'm currently trying to run this GH Action as part of a longer action that generates coverage and sends to Codacy. The relevant Codacy part of the YAML is:

      - name: Generate Coverage
        run: npm run coverage
      - name: Run codacy-coverage-reporter
        uses: codacy/codacy-coverage-reporter-action@v1
        with:
          api-token: ${{secrets.CODACY_TOKEN}}
          coverage-reports: coverage/lcov.info

This has worked as expected for over a year, but we've recently experienced issues specifically when using this Action and trying to send the lcov data back to Codacy. Currently, we keep getting results similar to the following:

--> Expected checksum
7c08e785c88ba02ad9311556e92f07657ccde38387f08989758c02c5508b1032a83c9f383b895a84138b7ec8d315c79e232c77887ca42fb7d998e16bf2178327  codacy-coverage-reporter-linux
 --> Actual checksum
7c08e785c88ba02ad9311556e92f07657ccde38387f08989758c02c5508b1032a83c9f383b895a84138b7ec8d315c79e232c77887ca42fb7d998e16bf2178327  codacy-coverage-reporter-linux
codacy-coverage-reporter-linux: OK
2024-06-17 15:24:38.060Z  info [ConfigurationRules] API base URL: https://api.codacy.com/  - (ConfigurationRules.scala:81)
2024-06-17 15:24:38.258Z  info [CommitUUIDProvider] CI/CD provider GitHub Actions found Commit UUID c285358a090f138405ec7fd85fef7b6449e64168  - (CommitUUIDProvider.scala:134)
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
2024-06-17 15:24:38.363Z  info [ReportRules] Parsing coverage data from: /home/runner/work/[private-repo-name]/[private-repo-name]/coverage/lcov.info ...  - (ReportRules.scala:41)
2024-06-17 15:24:38.363Z  warn [ReportRules] Report file /home/runner/work/[private-repo-name]/[private-repo-name]/coverage/lcov.info is empty  - (ReportRules.scala:59)
2024-06-17 15:24:38.363Z  info [ReportRules] 
To complete the reporting process, call coverage-reporter with the final flag.
 Check https://docs.codacy.com/coverage-reporter/#multiple-reports
 for more information.  - (ReportRules.scala:88)
2024-06-17 15:24:38.363Z error [CodacyCoverageReporter] No coverage data was sent  - (CodacyCoverageReporter.scala:28)

This is occurring despite seeing the existing unit and integration tests run, pass, and generate the coverage file. Any idea what may be causing the SLF4J issues?

cougrimes avatar Jun 17 '24 15:06 cougrimes