-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
mark mutable atomic_value_ptr members as CMS_THREAD_SAFE in [V]ParamererSetEntry #28331
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28331/12589
|
A new Pull Request was created by @slava77 (Slava Krutelyov) for master. It involves the following packages: FWCore/ParameterSet @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@Dr15Jones |
+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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
looking at the static analyzer results between CMSSW_11_0_X_2019-11-10-0000 and CMSSW_11_0_X_2019-11-10-2300, I conclude that this PR reduced the number of issues in the category "mutable member if accessed via const pointer " from 80.7K to 67.1K (17%). |
based on what's apparently false-positive reports of thread unsafety by the static analyzer.
I expect that this PR will substantially reduce the total count of warnings (IIUC, this count is replicated from every include and use case of [V]ParameterSetEntry)