SonarQube Scann is failing due to Error during parsing of coverage report /target/failsafe-reports:No such file or directory

[saifuddin tariwala]

Hi,

We recently upgraded SonarQube from 5.6 to 6.2.

After upgrade all my Sonar Builds are failing due to: 

Error during parsing of coverage report /target/failsafe-reports: /target/failsafe-reports (No such file or directory).

This is just a Sonar Scanner, no coverage I am running.

SonarQube Version: 6.2

sonar-maven-plugin:2.7.1

Is there any configuration changes we need to do?

Please help.

Thanks,

-Saif

[SK]

Hi

  Are you trying to run coverage first and then expecting Sonar scanner to read the report?  I had some issues with making sonar scanner read cppreports.  The issue was that the path should have been supplied in the ant path format. Maybe for coverage also, it expects somewhat similar?   

[saifuddin tariwala]

I am not trying to run coverage first.

This is just a sonar scanner task under the build.

Where should I provide an Ant Path?

This snanner build was running fine on SonarQube version 5.6 before.

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/d-8emxIFYdo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/6c67d6f4-04a2-4f36-9999-23d5c3cfaf06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sreeram Krishna]

Hi

   We'll need to see the sonar-project.properties.  From the error message it looks like Sonar scanner is trying to process the coverage report and it cannot find the report.  If you can confirm that's true, then instead of the path you've provided for the coverage report, that needs to be provided in a ant path format. 

Try to follow a pattern that's described here and see if that helps.  https://ant.apache.org/manual/dirtasks.html

[saifuddin tariwala]

That's True, Sonar scanner is trying to process the coverage report and it cannot find the report.

But, I never ran any Code Coverage Task, still it tries to look for the coverage report? why ?

I have the sonar-project.properties file, what property you want to confirm?

Thanks for you help.

[saifuddin tariwala]

I have the path for Jacoco report and Unit Test Report location,

But it is failing to find the failsafe report path, which I don't know how to provide?

[saifuddin tariwala]

One difference I notice as compare to our previous working SonarQube version 5.6 is,

Working Version 5.6: 

[INFO] Sensor GenericCoverageSensor

[INFO] Imported coverage data for 0 files
[INFO] Parsing /target/failsafe-reports
[WARNING] Cannot find IT coverage report to parse: /target/failsafe-reports
[INFO] Sensor GenericCoverageSensor (done) | time=13ms
[INFO] Sensor Sonar-Sonargraph-Plugin [3.5]

It report the coverage report unable to find as as "Warning"

Latest Version 6.2: 

[INFO] Sensor Generic Coverage Report
[INFO] Parsing /target/failsafe-reports
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.2:sonar (default-cli) on project rt: Error during parsing of coverage report /target/failsafe-reports: /target/failsafe-reports (No such file or directory) -> [Help 1]

So, even wothout providing any instaruction to run a coverage report, sensore trying to look for the coverage report and it failed, as there was no code coverage report available.
Now, How to disable this behavior, to avoid looking for Coverage report before it ran?

Please help.

Thanks,
-Saif

[saifuddin tariwala]

Hi All,

Can soenone help us pointing to the issue here?

We are planning to degrade to version 6.1 if nothing workout soon, as we are heavily dependent on SonarQube as a part of our daily workflow.

Any help/suggestion is much appreciated.

Thanks,

-Saif

[Julien HENRY]

Hi,

You probably have a wrong value configured for 'sonar.genericcoverage.itReportPaths'. This property was used by the generic coverage plugin and is now part of SonarQube 6.2. It is likely that the property was set in the UI prior your migration. Now the property is no more visible, but still processed for backward compatibility.

To confirm that, just open in a web browser:

http://myServer.ad1.prod:9000/api/properties?resource=rt

And check if you have sonar.genericcoverage.itReportPaths=/target/failsafe-reports

Then you have to use the WS API to remove the property. Something like:

curl -u myID:myPassword -X DELETE 'http://myServer.ad1.prod:9000/api/properties/sonar.genericcoverage.itReportPaths?resource=rt'

Then refresh the page in your web browser to verify there is no more value for sonar.genericcoverage.itReportPaths.

++

Julien

[saifuddin tariwala]

You are right Julien. 

This is exactly what happened.

Thanks for your respnse and time, I appreciate it.

regards,

-Saif

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7812bbc2-7c12-4607-8023-b7cb604aedbd%40googlegroups.com.