Hey Ben!
That’s pretty unexpected behavior. The next step after Computing Duplication Measures has nothing to do with coverage (it’s Compute size measures on new code), so the fact that supplying a coverage report (even a large one) causes there to be an issue is pretty weird.
I have a few thoughts:
- With the v25.2 Community Build, are you connecting it to your Postgres database or just using the embedded H2 database?
Could you double check your scanner logs to see if the coverage report is being indexed by the scanner? You can see every individual file indexed by the scanner by executing sonar-scanner -X.
If you see it being indexed, I would suggest excluding the file from analysis (sonar.exclusions) to see if that changes the behavior.
Should DB maintenance is never a bad idea.
Do you see any significant load (CPU, memory) on either your SonarQube server or your database when this happens?