Skip to content
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

Geant4Output2EDM4hep: allow reuse of collection names... again #1157

Merged

Conversation

wdconinc
Copy link
Contributor

@wdconinc wdconinc commented Aug 21, 2023

This seems to have gotten broken again here. We do NOT want to assign an empty collection since it overwrites the hits that are already in the collection; we just want to ensure that the named collection exists and the map should take care of the construction if it doesn't.

The ClientTest 'framework' doesn't easily allow for a unit test to prevent this from regressing (it's mostly based on regexes on failures), but please comment on ideas for tests there.

BEGINRELEASENOTES

  • Geant4Output2EDM4hep: allow use of identical collection names across multiple detectors

ENDRELEASENOTES

@wdconinc
Copy link
Contributor Author

Failing tests are in both cases FATAL +++ Exception while simulating: BitFieldElement 'x': out of range : -2147483648 for width 12 and not related to this PR:

They also occur on master, e.g. https://github.com/AIDASoft/DD4hep/actions/runs/5761723352/job/15620106338#step:4:5201.

@andresailer
Copy link
Member

Yes, the test failures are under investigation in #1153

@andresailer andresailer merged commit 81254ea into AIDASoft:master Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants