More violations in SonarLint 4.0.0.2018.10170711 compared to SonarCFamily 5.1 (build 10083)

sonarlint

(Frédéric Depale) #1

Hi,

I don’t understand because i have more violations in SonarLint 4.0.0.2018.10170711 compared to SonarQube 6.7.3 with SonarCFamily 5.1 (build 10083) and sonar-scanner-3.1.0.1141 .

Are these versions compatible ?

I have no errors in sonar-scanner :

sonar-scanner-3.1.0.1141-linux/bin/sonar-scanner -e -Dsonar.host.url=http://tosdc1tclapp11p.tosa.thales:9000 -Dsonar.projectName=OSFIR_LOP_INTEG_VSER_2 -Dsonar.cpd.exclusions=/CSC_SPV_IR_OSF0/ -Dsonar.projectVersion=1.0.0 -Dsonar.sourceEncoding=ISO-8859-1 -Dsonar.projectKey=OSFIR_LOP_INTEG_VSER_2 -Dsonar.cfamily.build-wrapper-output=/view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir/buildWrapper -Dsonar.projectBaseDir=/view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir/ -Dsonar.sources=SE_IAV/GENERATION/CSC_SE_IAV/Include,SE_IAV/GENERATION/CSC_SE_IAV/Src_

INFO: Option -e/–errors is no longer supported and will be ignored

INFO: Scanner configuration file: /repo_e2/usr/ThalesControl/SonarQube/SonarScanner/sonar-scanner-3.1.0.1141-linux/conf/sonar-scanner.properties

INFO: Project root configuration file: NONE

INFO: SonarQube Scanner 3.1.0.1141

INFO: Java 1.8.0_121 Oracle Corporation (64-bit)

INFO: Linux 2.6.32-642.6.1.el6.x86_64 amd64

INFO: User cache: /users/tc_osfir/.sonar/cache

INFO: SonarQube server 6.7.3

INFO: Default locale: "en_US", source code encoding: "ISO-8859-1"

INFO: Publish mode

INFO: Load global settings

INFO: Load global settings (done) | time=67ms

INFO: Server id: AWOXzV9M18gZqFi4iAW-

INFO: User cache: /users/tc_osfir/.sonar/cache

INFO: Load plugins index

INFO: Load plugins index (done) | time=59ms

INFO: Process project properties

INFO: Load branch configuration

INFO: Load branch configuration (done) | time=1ms

INFO: Load project repositories

INFO: Load project repositories (done) | time=388ms

INFO: Execute project builders

INFO: No TUSAR reports found for project: OSFIR_LOP_INTEG_VSER_2

INFO: Execute project builders (done) | time=58ms

INFO: Load quality profiles

INFO: Load quality profiles (done) | time=47ms

INFO: Load active rules

INFO: Load active rules (done) | time=989ms

INFO: Load metrics repository

INFO: Load metrics repository (done) | time=24ms

INFO: Project key: OSFIR_LOP_INTEG_VSER_2

INFO: ------------- Scan OSFIR_LOP_INTEG_VSER_2

INFO: Load server rules

INFO: Load server rules (done) | time=368ms

INFO: Base dir: /view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir

INFO: Working dir: /view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir/.scannerwork

INFO: Source paths: SE_IAV/GENERATION/CSC_SE_IAV/Include, SE_IAV/GENERATION/CSC_SE_IAV/Src

INFO: Source encoding: ISO-8859-1, default locale: en_US

INFO: Calculating dynamically TUSAR language suffixes: []

INFO: Dynamically TUSAR language suffixes: []

INFO: Index files

INFO: 29 files indexed

INFO: Quality profile for c: C_NONE

INFO: Quality profile for cpp: IRST_C++

INFO: Sensor SonarJavaXmlFileSensor [java]

INFO: Sensor SonarJavaXmlFileSensor [java] (done) | time=1ms

INFO: Sensor TUSAR Measures Sensor [tusar]

INFO: Sensor TUSAR Measures Sensor [tusar] (done) | time=0ms

INFO: Sensor TUSAR Tests Sensor [tusar]

INFO: Sensor TUSAR Tests Sensor [tusar] (done) | time=0ms

INFO: Sensor TUSAR Coverage Sensor [tusar]

WARN: TUSAR Coverage Sensor is disabled. TUSAR Coverage reports are not supported since SonarQube 6.7.x

INFO: Sensor TUSAR Coverage Sensor [tusar] (done) | time=1ms

INFO: Sensor CFamily [cpp]

INFO: Available processors: 8

INFO: Using 1 thread for analysis according to value of "sonar.cfamily.threads" property.

INFO: Using build-wrapper output: /view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir/buildWrapper/build-wrapper-dump.json

INFO: 0 compilation units analyzed

INFO: PCH: 0 + 0 + 0 , 0 - 0 - 0 - 0

INFO: FS: 3903 lookups

INFO: PPH: 0 files, 0 bytes, 0 hits, 0 queries

INFO: Available processors: 8

INFO: Using 1 thread for analysis according to value of "sonar.cfamily.threads" property.

INFO: Using build-wrapper output: /view/tc_osfir_OSF_DEV_V1_int_VSER/vobs/osfir/buildWrapper/build-wrapper-dump.json

INFO: 0 compilation units analyzed

INFO: 5 compilation units analyzed

INFO: 10 compilation units analyzed

INFO: 14 compilation units analyzed

INFO: PCH: 0 + 0 + 0 , 3892 - 0 - 0 - 0

INFO: FS: 264832 lookups

INFO: PPH: 308 files, 4555032 bytes, 2063 hits, 2371 queries

INFO: Sensor CFamily [cpp] (done) | time=44852ms

INFO: Sensor Zero Coverage Sensor

INFO: Sensor Zero Coverage Sensor (done) | time=51ms

INFO: Sensor CPD Block Indexer

INFO: Sensor CPD Block Indexer (done) | time=0ms

INFO: SCM Publisher is disabled

INFO: 8 files had no CPD blocks

INFO: Calculating CPD for 21 files

INFO: CPD calculation finished

INFO: Analysis report generated in 1343ms, dir size=467 KB

INFO: Analysis reports compressed in 227ms, zip size=148 KB

INFO: Analysis report uploaded in 197ms

INFO: ANALYSIS SUCCESSFUL, you can browse http://tosdc1tclapp11p.tosa.thales:9000/dashboard/index/OSFIR_LOP_INTEG_VSER_2

INFO: Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report

INFO: More about the report processing at http://tosdc1tclapp11p.tosa.thales:9000/api/ce/task?id=AWkQ70LiZfpVtDx8K_8m

INFO: Task total time: 52.527 s

INFO: ------------------------------------------------------------------------

INFO: EXECUTION SUCCESS

INFO: ------------------------------------------------------------------------

INFO: Total time: 54.227s

INFO: Final Memory: 33M/907M

INFO: ------------------------------------------------------------------------

Started calculate disk usage of build

Finished Calculation of disk usage of build in 0 seconds

Started calculate disk usage of workspace

Finished Calculation of disk usage of workspace in 0 seconds

Finished: SUCCESS

Thanks,

Frédéric


(Massimo Paladin) #2

Hi @frederic.depale,

did you update project bindings to make sure that SonarLint is “in sync” with your project in SonarQube?


(Frédéric Depale) #3

Hi Massimo,

Thank you but yes, i updated project bindings and the synchronize is ok.
Would you have another reason ?
According to you experience, the number of violation with SonarLint and SonarSource is already equal ?

Best regards,
Frédéric


(Massimo Paladin) #4

Hi @frederic.depale,

could you please provide an example of mismatch?


(Frédéric Depale) #5

Hi Massimo,

For example, the rule “remove use of union” is detected by SonarLint and not by SonarQube.

log_sonar_scanner_irstinde__pe_drv.txt (51.5 KB)

Frédéric


(Massimo Paladin) #6

Hi @frederic.depale,

for header files there could be mismatches due to the fact that:

  • in SonarLint header files are analyzed as single entities
  • in sonar-scanner header files are analyzed through the compilation unit files including them (i.e. .cpp, .c, …)

Which means that as a matter of fact for header files you would not get a 1 to 1 link between SonarQube and SonarLint.


(Frédéric Depale) #7

Hi Massimo,

thank you for your explanations and have a nice week-end !

Frédéric