Code coverage not taking gcov while sonar-scanner is running

[cdatt1989 (Chandra Datt)]

Must-share information (formatted with Markdown):

• which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  SonarQube version 9.9
• how is SonarQube deployed: zip, Docker, Helm
  zip
• what are you trying to achieve
  need to get coverage report of gcov
• what have you tried so far to achieve this
  sonar-scanner -X -Dsonar.cfamily.build-wrapper-output=worker/bw-output -Dsonar.cfamily.threads=8 -Dsonar.cfamily.cache.enabled=false -Dsonar.cfamily.gcov.reportPaths=src/gcov_files -Dsonar.projectKey=“Project:CPP” -Dsonar.projectName=Project -Dsonar.sources=src -Dsonar.projectVersion=1.0 -Dsonar.host.url=xxxx -Dsonar.login=xxx
  Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

[Colin]

Okay. What happens after? You’ll need to share more than just the analysis command – does some coverage get reported? None at all? What do the logs say?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube / SonarCloud, the first place you should look is the scanner logs. Where do I find the scanner logs? This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the scanners, either directly or wrapped by one of many integrations, such as the SonarScanner for Jenkins, SonarScanner for Azure DevOps, SonarQube/SonarCloud GitHub Actions or SonarQube / SonarCloud Bitbucket Pipes. …

[cdatt1989 (Chandra Datt)]

Hi Colin, Thanks for your valuable response. The issue got resolved. I was doing a silly spelling mistake
Instead of sonar.cfamily.gcov.reportsPath I was using *sonar.cfamily.gcov.reportPaths parameter. Also there was no error occurring during the sonar scan for incorrect parameter.