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 T0 DQM crash. Remove online uGT DQM module from the offline #19241
Fix T0 DQM crash. Remove online uGT DQM module from the offline #19241
Conversation
…rashes at the T0.
A new Pull Request was created by @thomreis (Thomas Reis) for master. It involves the following packages: DQMOffline/L1Trigger @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @rekovic, @vanbesien, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@dmitrijus @davidlange6 This is not yet approved by the uGT folks and should only be merged after the green light by them or in case of emergency. |
what T0 DQM crash is this referring to?
… On Jun 15, 2017, at 11:05 AM, Thomas Reis ***@***.***> wrote:
@dmitrijus @davidlange6 This is not yet approved by the uGT folks and should only be merged after the green light by them or in case of emergency.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The thread name in the HN link posted above is "Jobs Exceeding maxRSS Observed in Replay for 923p1". |
plase test |
+1 |
The tests are being triggered in jenkins. |
Comparison job queued. |
@dmitrijus @davidlange6 This got the green light from @apana and Manfred. They are OK to remove the module from offline. @rekovic can you please take a look and sign this? |
Comparison is ready Comparison Summary:
|
+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 requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 |
Remove the online uGT DQM module from the offline sequence to avoid crashes at the T0.
The large histograms used too much memory and caused crashes.
https://hypernews.cern.ch/HyperNews/CMS/get/recoDevelopment/1532/1/1.html