-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CE log is flooded with DEBUG and ERROR entries #1640
Comments
@johaag thank you for your report.
@guwirth I suggest just to reduce the logging amount. E.g. UnitTestMeasuresStep doesn't log at all (although it's based on some other [internal] technology). I'll provide the PR. I believe it would match the 1.2.1 milestone well. "optimize loggin" is one of its main aims. |
@ivangalkin thank you so much for taking care of this issue and fixing it so promptly! Your change looks good to me. Great to see that we will get a fix in 1.2.1. |
@johaag you can try with latest snapshot. |
@ivangalkin and @guwirth, checked with latest snapshot. LGTM. Thanks a lot for taking care! |
Description
After updating to sonar-cxx v1.2.0 on SonarQube 6.7.6 LTS Enterprise Edition, a lot of DEBUG and ERROR messages occur in the CE log.
During portfolio calculation (VIEW_REFRESH) for each portfolio calculated the following log entries are created (log level DEBUG):
These log entries are created also for empty portfolios and for portfolios containing projects which do not use sonar-cxx.
Similar entries are created during processing of scan results (REPORT):
These log entries are created for each file of a project, regardless of the language and if sonar-cxx is used by the project.
This is a lot of noise in the CE log file and especially the ERRORs are a problem from our point of view.
Steps to reproduce the problem
Please provide the steps required to reproduce the problem
Install SonarQube 6.7.6 LTS Enterprise Edition along with sonar-cxx 1.2.0
Set log level for CE to DEBUG
Trigger portfolio calculation via Web API
api/views/run
Scan a project and upload it to SonarQube
Observe CE log entries in
logs/ce.log
Expected behavior
Log entries should only be created for files and projects which are analysed by sonar-cxx.
Actual behavior
Log entries are created for any file and project.
Known workarounds
None.
LOG file
See above.
Related information
The text was updated successfully, but these errors were encountered: