-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Replace getProcessParameterSet function #9869
Replace getProcessParameterSet function #9869
Conversation
Replace the function getProcessParameterSet in DQMServices. This function is being removed from the CMSSW Framework because it does not work properly with SubProcesses and causes issues with multithreading. The replacement should yield identical behavior to what was originally there (except now it works in a SubProcess job).
A new Pull Request was created by @wddgit (W. David Dagenhart) for CMSSW_7_6_X. Replace getProcessParameterSet function It involves the following packages: DQMServices/Components @cmsbuild, @danduggan, @deguio can you please review it and eventually sign? Thanks. |
please test |
+1 |
The tests are being triggered in jenkins. |
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 |
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 |
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 |
+1 |
Replace getProcessParameterSet function
Replace the function getProcessParameterSet
in DQMServices. This function is being removed
from the CMSSW Framework because it does not work
properly with SubProcesses and causes issues
with multithreading. The replacement should
yield identical behavior to what was originally
there (except now it works in a SubProcess job).