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
migrate to concurrent DQM #21766
migrate to concurrent DQM #21766
Conversation
An alternative implementation of #21764, for reference. |
The code-checks are being triggered in jenkins. |
@cmsbuild, please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21766/2730 |
The tests are being triggered in jenkins. |
A new Pull Request was created by @fwyzard (Andrea Bocci) for master. It involves the following packages: DQMOffline/RecoB @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @jfernan2, @vanbesien can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
3caf4f9
to
883af21
Compare
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21766/2731 |
Pull request #21766 was updated. @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @jfernan2, @vanbesien can you please check and sign again. |
@cmsbuild, please test |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
I understand that @VinInn is OK with these changes. @vazzolini, @kmaeshima, @dmitrijus, could please sign or comment ? |
+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 |
This pull request is causing a crash in the IBs. The problem is DTSegment2DSLPhiQuality is a legacy EDAnalyzer which does NOT inherit from DQMEDAnalyzer. The module is calling directly into the DQMStore at global begin Run and happens to do it at the exact same time as PrimaryVertexMonitor. |
DTSegment2DSLPhiQuality did not cause a problem previously because the DQMEDAnalyzers were all stream modules so they filled their histograms at streamBeginRun and streamBeginLuminosityBlock which happen after their global counterparts. |
DTRecHitQuality is also causing crashes in the beginRun for the same reason as DTSegment2DSLPhiQuality. |
@fwyzard @Dr15Jones given that we need to converge for pre4, I will revert the PR in case we do not have quickly a fix |
Do I understand correctly that before any module is migrated to the new concurrent DQM |
Reverting this PR will not solve the issue... I will migrate/disable DTSegment2DSLPhiQuality later today. |
Correct. |
No description provided.