Sonarqube 6.2 ERROR - Could not complete symbolic execution: reached limit of 16000 steps

[loris....@xpeppers.com]

Hi,

I'm using JDK 1.8, Sonarqube 6.2 with sonar java plugin version 4.7.1.9272 and running sonarlint (version 2.1.0.566) in connected mode to the SQ 6.2:

sonarlint-cli-2.1.0.566/bin/sonarlint -X -u --src "**/src/main/java/**" --tests "**/src/test/**"

The analysis is finished and the report is created, but looking at the log I get this error kind of error more than once:

DEBUG: Could not complete symbolic execution: 
org.sonar.java.se.ExplodedGraphWalker$MaximumStepsReachedException: reached limit of 16000 steps for method

Any help would be greatly appreciated!

Regards,
Loris

[Nicolas Peru]

Hi Loris, 

Nothing to be worried about, this is a debug log. This is just a safe mechanism in the dataflow engine to avoid computing endlessly when the exploration of a method takes too many steps so the dataflow engine could finish in a timely fashion. 

The only drawback is that some issues may not have been found.

We are working hard to not overcome this limit too often but if you want better accurate results you may want to reduce complexity and size of the methods mentionned by those logs.

Cheers, 

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/090b01b9-f077-4d23-8831-d61a44d8b7ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Nicolas PERU | SonarSource

Senior Developer
http://sonarsource.com

https://twitter.com/benzonico

[toni...@gmail.com]

Hi Nicolas,

Thanks for the information.

In my sonar environment, the system prints a lot of logs like this.

From the log, it seems the system took about 2 hours to analyze one java file.

Did the system take 2 hours to analyze one java file?

Or it is just a debug log, the system did not take 2 hours to analyze one java file.

Thanks in advance.

Regards,

Tony

Nicolas Peru於 2017年4月12日星期三 UTC+8下午10時20分09秒寫道：

[toni...@gmail.com]

Hi there,

I remove the java file and run it again. It saves 2 hours to execute the job.

So I think it is not just a debug log, the system really takes a lot time to analyze the java file.

Any suggestions are welcome.

Thank you.

toni...@gmail.com於 2017年7月23日星期日 UTC下午12時45分27秒寫道：

[Tibor Blenessy]

Hello Tony,

please do not reply on old threads. Start a new thread describing your issue and also please provide version of SonarJava analyzer you are using to analyze your project.

Best regards

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/f08844ea-9122-482a-a7a8-cbe655213d94%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Tibor Blenessy | SonarSource

SonarJava Developer

http://sonarsource.com