-
Notifications
You must be signed in to change notification settings - Fork 4.6k
DQM: Remove concurrent-lumi blocking DQM Modules. #30111
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
Conversation
|
The code-checks are being triggered in jenkins. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30111/15875
|
|
please test |
|
The tests are being triggered in jenkins. |
|
A new Pull Request was created by @schneiml (Marcel Schneider) for master. It involves the following packages: DQM/EcalPreshowerMonitorModule @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
@schneiml shall we include this in CMSSW_11_2_0_pre1? |
|
@silviodonato no, we need at least Ecal properly fixed before this can go in (@tanmaymudholkar ?) Then, we also need a proper fix or removal for |
|
hold |
|
Pull request has been put on hold by @schneiml |
|
Comparison is ready Comparison Summary:
|
|
please test |
|
The tests are being triggered in jenkins.
|
|
+1 |
|
Comparison job queued. |
|
If I understand correctly, This means that after having merged #31354 the list of the offending modules will be After having merged #31354, I would suggest @cms-sw/dqm-l2 to update this PR, re-adding the modules that have been migrated. |
|
Comparison is ready Comparison Summary:
|
|
yes, at least I think I have fixed it (well I have followed the guidelines maybe I made something wrong?) |
yes, thanks. ? |
|
@silviodonato the owner of this PR is no longer in CMS (@schneiml ), so I understand I cannot modify this PR. I may create a new equivalent on Monday once I come back from Holidays if it is still on time. Thanks |
Yes, sure. Thanks @jfernan2 ! |
|
@silviodonato I managed to get a stable connection and made the PR, so you can close this one. |
|
@jfernan2 thank you! |
PR description:
This PR removes (some?) of the remaining modules blocking concurrent lumisections in production jobs.
I ran a random 136 relval with concurrent lumis enabled and got these modules reported:
(Update:
DetStatusis gone (thanks @mmusich !), and after #30187,EcalDQMonitorTaskis gone as well.ESIntegrityTaskremains, however.)DetStatusis not DQM related, I removed the others from the sequences. There might be more modules that are not used in this specific workflow.Overall, some of these modules are quite important and we don't want to merge this PR. But it gives an idea of what these modules do and allows to try actually enabling concurrent lumis.
(@silviodonato update:
RPCDcsInfo rpcDcsInfoupdated with #31056ALCARECOTkAlMinBiasDCSFilter-> updated with #30124)
PR validation:
None, so far; not supposed to be merged for now.