-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Initialise the errors_ data member of SiPixelDigiErrorsSoAFromCUDA [12.3.x] #38478
Initialise the errors_ data member of SiPixelDigiErrorsSoAFromCUDA [12.3.x] #38478
Conversation
Prevents reading from uninitialised memory when the first event of a job has zero error words. Fixes a crash observed at HLT during data taking.
type bug-fix |
A new Pull Request was created by @fwyzard (Andrea Bocci) for CMSSW_12_3_X. It involves the following packages:
@jpata, @cmsbuild, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
backport #38476 |
urgent |
enable gpu |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4868e8/25709/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
+reconstruction |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. 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) |
+1 |
PR description:
Initialise the
errors_
data member of theSiPixelDigiErrorsSoAFromCUDA
producer.Prevents reading from uninitialised memory when the first event of a job has zero error words, and fixes a crash observed at HLT during data taking.
PR validation:
Without this fix, it is possible to reproduce the error observed online running over the "error stream" events that triggered it.
With this fix, no crash is observed after running 30+ times on the same input.
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport of #38476, needed for data taking.