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
Fix unsafe dqmed analyzers for710pre6 #3262
Fix unsafe dqmed analyzers for710pre6 #3262
Conversation
…nd JPT related parts
… functionality from OfflineClient now in other analyzers, take out of sequence
… to make it reproducible
Conflicts: HLTriggerOffline/Common/python/HLTValidationHarvest_cff.py
…emoval of JPTJets
Added "const" qualifier to getTypeString function for thread safety.
…yzer to be able to handle the transition to the threaded fwk while not all the product used are thread safe
This reverts commit b083662.
A new Pull Request was created by @deguio for CMSSW_7_1_X. Fix unsafe dqmed analyzers for710pre6 It involves the following packages: DQMOffline/JetMET @ojeda, @danduggan, @rovere, @cmsbuild, @nclopezo, @deguio, @Degano can you please review it and eventually sign? Thanks. |
+1 |
thanks |
Being tested... |
DQM -- Fix unsafe dqmed analyzers for710pre6
…710pre6 DQM -- Fix unsafe dqmed analyzers for710pre6
new layer class (thread_unsafe::DQMEDAnalyzer) now available. the classes which use unsafe ES products which have already migrated to the DQMEDAnalyzer interface have been modified to inherit from this new class in order:
the following pull requests are superseeded by this one: