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
Use a safer syntax in Geometry/ForwardCommonData #38672
Use a safer syntax in Geometry/ForwardCommonData #38672
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38672/30964
|
A new Pull Request was created by @perrotta (Andrea Perrotta) for master. It involves the following packages:
@civanch, @Dr15Jones, @bsunanda, @makortel, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob 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-a5c159/26107/summary.html Comparison SummarySummary:
|
+geometry |
Should safer syntax be applied to HGCAl, |
@cmsbuild please test workflow 39434.911 Just to make sure that Phase-2 DD4hep runs after this clean up. |
The file you are pointing at is the one from which all other config are cloned. I don't think there is anything safer for it, unless we decide to clone it further from somewhere else, which is beyond the scope of this fix |
Hi @perrotta |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a5c159/26117/summary.html Comparison SummarySummary:
|
+Upgrade Technical PR. Existing phase-2 DD4hep workflow, 39434.911_TTbar_14TeV+2026D88, runs fine. |
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:
Solves #38604
It migrates to a safer syntax (no explicit types for the cloned parameters) the following two files
While doing so I also fixed two conceptual mistakes (attempt to modify a module in a different configuration):
This wasn't needed anyhow, because the same modifier was already (correctly) applied to the cloned module
For the same reason I removed the customization from
as it should more safely rely on the one already present in the cloned module instead
Attn @bsunanda
PR validation:
It builds succesfully
No changes expected whatsoever