-
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
add non-empty checks in DAClusterizer to avoid reading null refs #44281
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44281/39302
|
A new Pull Request was created by @slava77 for master. It involves the following packages:
@cmsbuild, @jfernan2, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2ad74e/37881/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. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
@cmsbuild please test workflow 11602.0 for CMSSW_14_1_UBSAN_X |
-1 Failed Tests: RelVals RelValsThe relvals timed out after 4 hours. |
step3 log of wf 11602.0 is now clean of the |
@cmsbuild please test |
@cmsbuild please abort |
@cmsbuild please test workflow 11602.0 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2ad74e/37935/summary.html Comparison SummarySummary:
|
these are apparently unrelated. IIUC, the UBSAN issue in this case is mostly false-positive: while the null reference is technically used for a transient value ptr assignment, the values are never used. |
+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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
to address #44277