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
Removing obsolete code from CaloLayer1Setup #35940
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35940/26341
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35940/26344
|
A new Pull Request was created by @BenjaminRS (Benjamin Radburn-Smith) for master. It involves the following packages:
@cmsbuild, @rekovic, @cecilecaillol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
urgent |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-bcb20f/20180/summary.html Comparison SummarySummary:
|
+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 (and backports should be raised in the release meeting by the corresponding L2) |
@BenjaminRS Should this be backported to 12_0_X to replace #35877? |
Hi @qliphy - this can be backported to replace the previous PR if you wish; however @perrotta mentioned in this comment that the backport with the other solution can remain. Which is the preferred course of action? |
@BenjaminRS Fine with me with the proposal from @perrotta as for 12_0_X |
@BenjaminRS can I also ask you to include "CaloLayer1Setup" in the PR title? It's best to have the PR titles as descriptive as possible. |
Hi @tvami -- sorry for that, I didn't realise it was so easy to change :) |
+1
|
PR description:
This PR removes obsolete code from the CaloLayer1 area which has been causing spurious elog warnings as described in Issue#34309. As suggested in this comment to PR#35873 I have removed the if else statement which was now obsolete.