Skip to content

Conversation

@codykaup
Copy link

I recently setup code coverage with Golang and hit a snag in how our coverage reports were generating. Turns out, it was related to the module name we used. Since it didn't match the directory structure of our project, the file in our repository wasn't being found and resulting in the following error:

info [ReportRules] Parsing coverage data from: /my/coverage/file.out ...  - (ReportRules.scala:41)
info [ReportRules] Coverage parser used is com.codacy.parsers.implementation.GoParser$@1f392a2f  - (ReportRules.scala:46)
warn [GitFileNameUpdaterAndFilter] File: Ignoring mymodule/XX.go for coverage calculation. No matching file found in the repository.  - (GitFileNameUpdaterAndFilter.scala:24)
error [CodacyCoverageReporter] No coverage data was sent  - (CodacyCoverageReporter.scala:28)

Note: I changed some of the details but the directory structure is my-module/go.mod

👀 Live preview

http://127.0.0.1:8000/coverage-reporter/uploading-coverage-in-advanced-scenarios/#golang

Screenshot 2024-06-18 at 4 44 37 PM

🚧 To do

  • If relevant, include the Jira issue key at the end of the pull request title
  • Perform a self-review of the changes
  • Fix any issues reported by the CI/CD

@codykaup codykaup requested a review from a team as a code owner June 18, 2024 21:55
@RaquelHipolito RaquelHipolito self-assigned this Nov 4, 2024
@codykaup
Copy link
Author

Closing this out since it's been a year with no movement. 🤷‍♂️

@codykaup codykaup closed this Jun 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants