We recently had an MSBuild analysis that was previously taking ~10 min begin to take 1hr+ with minimal code changes, and we are trying to narrow down possibilities.
Unfortunately, the configuration that runs this analysis in TeamCity is somewhat difficult to reproduce locally, so it is slow & difficult to test out changes to the conifguration.
- MSBuild SonarScanner: 4.4.2
- SonarQube Server: 7.9.1
Project size: 100k LOC
(I will be attempting to run the analysis with an upgraded MSBuild Scanner version, but it will take some time to configure)
In the meantime, I was hoping some insight could be provided into some of the DEBUG messages we are receiving in the log.
I cannot post the full log due to corporate policy, but I can provide a summary:
Lines 1-10000: seemingly regular output
Lines 10k-2mil (that’s right, 2 million):
]16:47:06.110 DEBUG: file=C:\[path-to-project]\.git\objects\pack, isRacyClean=false, read=2020-10-05 16:42:08.547000000, lastModified=2020-10-05 16:36:14.747740000, delta=353799260000 ns, racy<=2502500 ns 16:47:06.110 DEBUG: file=C:\[path-to-project]\.git\objects\pack, is unmodified
repeated verbatim (only the pre-“DEBUG” timestamp changes)
Last 20 lines: successful analysis
These 2 million identical lines appear to be occurring during a CPD analysis, as this is the message after these 2mil lines are repeated:
16:47:06.622 INFO: 3/3 files analyzed 16:47:07.109 INFO: 71 files had no CPD blocks
Some followup questions on this error:
.git files being analyzed?
Would the size of the pack file influence this debug message being repeated? (This project is part of a much larger monorepo)
Are there any rules I can disable that might be affecting this?
Let me know if there’s any more information I can provide. Thank you!