-
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
[nT2] zero-initialisation of TotemT2Digi members #39149
Conversation
Zero-initialisation of TotemT2Digi members
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39149/31726
|
A new Pull Request was created by @forthommel (Laurent Forthomme) for master. It involves the following packages:
@jpata, @cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
As this PR is purely technical and could prevent some unassigned values and memory corruption, can we aim at a fast merge? |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ec08c5/27051/summary.html Comparison SummarySummary:
|
+reconstruction
|
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:
This PR ensures all members of the TotemT2Digi object are zero-initialised, following the discussion in #38986 for equivalent rechits.
PR validation:
Code compiles and runs.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for: N/A