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
Utilities/StaticAnalyzers: Add CMS_SA_ALLOW exceptions on Static Analyzer checks involving Decls. #28630
Utilities/StaticAnalyzers: Add CMS_SA_ALLOW exceptions on Static Analyzer checks involving Decls. #28630
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28630/13173
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28630/13174
|
@gartung could you give an example, as a comment in this pull request, on what new declarations can be marked? |
A new Pull Request was created by @gartung (Patrick Gartung) for master. It involves the following packages: Utilities/StaticAnalyzers @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
CMS_SA_ALLOW can be used before these declarations Stand alone checkers
CatchAll checker:
Function checker:
In a CMS data class: Before a const member function declaration where
Before a mutable member declaration. |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
test with cms-sw/cmsdist#5445 |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@gartung what is the state of this? Were you able to get the annotation of |
Yes the putting CMS_SA_ALLOW in front of the try statement will suppress the warning about catch (...) I tested it on the try catch in FWCore/Services and it works. |
Making vetos for the other checkers can be in another pull request. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos, @silviodonato (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Allows the user of cms threads safety macro CMS_SA_ALLOW in declarations that should be allowed to suppress the warning associated with the static analyzer check. This is done to reduce the volume of warnings in the static analyzer reports.