-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
A safe guard on GEM DQM harvester #39060
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39060/31562
|
A new Pull Request was created by @quark2 for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c667a9/26822/summary.html Comparison SummarySummary:
|
urgent
|
+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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
PR description:
There is an issue with too large memory consumption in the GEM DQM harvester procedure (#38976). To fix this issue, additional lines are added to suppress the too high number of chambers. This fix is temporary because the origin of the too large number is still missing. This is why I called it a 'safe guard.'
PR validation:
The code of the run issued in #38976 is run again, and I've checked that the memory usage (RSS) is reduced.