Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
cougrimes opened this issue Jun 17, 2024 · 1 comment
Labels
jira-issue Issue tracked on JIRA

Comments

@cougrimes
Copy link

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?

@github-actions github-actions bot added the jira-issue Issue tracked on JIRA label Jun 17, 2024
@github-actions github-actions bot changed the title Coverage generates but action cannot properly send back to Codacy [TCE-1015] Coverage generates but action cannot properly send back to Codacy Jun 17, 2024
Copy link

Internal ticket created : TCE-1015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira-issue Issue tracked on JIRA
Projects
None yet
Development

No branches or pull requests

1 participant