We have the following
Sonarqube Version 10.3
Sonarqube Scanner CLI 6.2.1.4610
C Build Wrapper Version 6.50
sonar scan for c take most time and log entry is
13:05:55 07:35:55.365 INFO [pool-5-thread-10] /home/jenkins/agent/workspace/abc.c
13:10:31 07:40:27.851 INFO PCH: unique=0 use=0 (forceInclude=0,throughHeader=0,firstInclude=0) out of 1002 (forceInclude=0,throughHeader=0)
13:10:31 07:40:27.851 INFO Z3 refutation rate: 61 out of 722
We indeed have a way to disable Z3 refutation, but it is an internal flag, only intended for us to understand potential issues with the analyzer.
Before sharing this flag with you, we would need to understand why you need it. Could you share with us an analysis log and explain what problem you’re attempting to solve by disabling it?
(note that, in addition to decreasing accuracy, disabling refutation may have a negative impact on performance).
We are aware of that it may cause degradation and issues.
We have a mono repo that is c based and it takes very long time to perform the scan , causing whole CI to take long time, we were to disable the scan but found want to try this before that, as it’s worst to have no scan
Could you still please share the log with us? I’m sending you a private message if you don’t want to share it publicly. Then I’ll share with you the way to disable the refutation stage.
Additionally, instead of having no scan, it is possible to disable all rules based on symbolic execution and see if it has an impact. But it is a more drastic change than just disabling Z3 refutation.
Thanks for all the information and the help but excluidng some files and disabiling some rules helped us speed up the scan. we do not need to disable z3 refutation in sonar.