[NGT] Fix content of SiPixelClusterSoA for empty Pixel Detector#50900
Conversation
|
type ngt |
|
type bug-fix |
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50900/49258
|
|
A new Pull Request was created by @JanGerritSchulz for master. It involves the following packages:
@Moanwar, @cmsbuild, @jfernan2, @mandrenguyen, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
enable gpu |
|
test parameters:
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
Max Memory Comparisons exceeding threshold@cms-sw/core-l2 , I found 2 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
|
|
+1 |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50900/49266
|
|
@cmsbuild, please test |
|
So, for future reference: |
|
-1 Failed Tests: RelVals Failed RelValsAMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
|
the failure is related to #42470 (and happens in step3, step3-like the step2 --previously failing-- now runs correctly) |
|
ignore tests-rejected with ib-failure |
|
+1 |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (test failures were overridden). This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @ftenchini, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
This PR is introducing the zero-initialization of the
SiPixelClusterSoAfor events with zero digis in the pixel detector. It fixes an issue that is arising later in the CA pixel tracking when the (previously wrong) values of the SoA are used, leading to crashes. This is described in detail in #50881 .PR validation:
It is a minor change that only affects empty events in the pixel tracker. I tested on the previously crashing workflow
34090.203, which runs after these changes. For any further validation the bot-tests should be sufficient.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:
Not a backport.