fix(ci): ubsan.supp: implicit-integer-sign-change in edm4hep::ObjectID #1685
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Capybara summary for PR 1685
|
veprbl
approved these changes
Jan 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
This PR fixes an UBSan error external to our code, showing up e.g. https://github.com/eic/EICrecon/actions/runs/12128923399/job/33816533286?pr=1635#step:8:880
EDM4hep defines CollectionID as signed int32_t, https://github.com/key4hep/EDM4hep/blob/v00-10-05/edm4hep.yaml#L111, but podio defines it as unsigned uint32_t, https://github.com/AIDASoft/podio/blob/v01-01/include/podio/ObjectID.h#L25. This is an issue as of podio-0.17.1, AIDASoft/podio@ac086e0, and disappears with EDM4hep-0.99 which removed the edm4hep::ObjectID component.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.