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
DT DQM legacy modules removal #29784
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29784/15241
|
A new Pull Request was created by @jfernan2 for master. It involves the following packages: DQM/DTMonitorClient @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
The tests are being triggered in jenkins. |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+dqm |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR tries to asses the issue #25090 in what concerns DT DQM Legacy modules.
The four conflicting classes:
DTDataIntegrityTask
DTDCSByLumiTask
DTResolutionAnalysisTask
DTSegmentAnalysisTask
are reconfigured to clear any conflicting module with concurrent LS or dropped their usage from DQM Offline configurations, leaving all the vs LS plots ONLY for DQM Online and removing them from DQM Offline.
The results imply a drop of 71 plots from workflows. Some other cleaning of the code has been done in parallel
PR validation:
Tested for DQM Online stand alone and with:
runTheMatrix.py -l limited
if this PR is a backport please specify the original PR and why you need to backport that PR:
No backport is foreseen
(Partially) Resolves #25090