Issue with sonarqube-check after upgrade from 2025.2.0 to 2025.3.0

[Colin]

Hey Andrii,

I believe that what you’re seeing in the web.log is a red herring.

You should have timestamps available in your scanner logs. What is taking long?

Need suggestions on speeding up sonar

I think a first good step would be to turn on the frontend analysis, and figure out which sensors are taking the longest. Could you try to look at the time information in the analysis console? For example: # if you have saved your scanner logs in an analyze.log file $ grep 'time=' analyze.log ... INFO: Sensor JavaSquidSensor [java] (done) | time=210234ms INFO: Sensor CSS Rules [cssfamily] (done) | time=3ms INFO: Sensor C# Properties [csharp] (done) | time=0ms INFO: Sensor SurefireSensor [java…