-
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
small technical fix in PixelVertexCollectionTrimmer #32919
small technical fix in PixelVertexCollectionTrimmer #32919
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32919/21146
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages: RecoPixelVertexing/PixelVertexFinding @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
(error in the tests is not related to this PR) |
Would it be possible to restart the tests? |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b83cc7/12961/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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
A test of mine with an incorrectly-configured path ended with a segmentation violation from
PixelVertexCollectionTrimmer
.This can occur because the latter producer assumes that the input collection of vertices is non-empty (see here).
The PR implements a simple way to avoid the segfault.
PR validation:
Update works as expected in the user test where the crash occurred.