Marked DataProxy as thread safe #11192
Conversation
The static analyzer was picking up DataProxy as being thread-safe. Applied the appropriate annotation to tell the analyzer the mutable was safe because it is protected by a mutex shared by all EventSetup components.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_7_6_X. Marked DataProxy as thread safe It involves the following packages: FWCore/Framework @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. |
|
please test |
|
+1 |
|
The tests are being triggered in jenkins. |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
1 similar comment
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
Marked DataProxy as thread safe
The static analyzer was picking up DataProxy as being thread-safe. Applied the appropriate annotation to tell the analyzer the mutable was safe because it is protected by a mutex shared by all EventSetup components.