-
Notifications
You must be signed in to change notification settings - Fork 184
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
[DD4Hep] Update to latest changes from master branch #5274
Conversation
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_11_0_X/master. @cmsbuild, @smuzaffar, @mrodozov can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 3bca066 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test testDD4hepExpandedView had ERRORS |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
please test |
The tests are being triggered in jenkins. |
Pull request #5274 was updated. |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 544a4b8 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test SiStripDCS_O2O_test had ERRORS |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@ianna , can you please look at this unit test GeometryDTGeometryBuilderTestDriver? Log shows [a]. @fabiocos if no objections then we can merge it in to DEVEL IBs so that Ianna can test it?
|
@smuzaffar and @fabiocos - it looks like the difference reported is unrelated to DD4hep version.
I'd say we merge the new version and I'll update the reference for the test. |
@ianna the difference is at the level of numerical rounding I would say, i.e. how well we approximate 0. Anyway why do you say that it is unrelated to DD4hep version? It changes when changing the external library, probably a tiny numerical effect, but that we do not observe otherwise, no? Fine for me to merge it in the DEVEL IB, but it would be good to have the unit test fixed in parallel before integrating in the master branch, it is not good to have too many failures around (and we have already several of them for other reasons). It would be good anyway to understand the cause of this difference, or understand how to get it under control. |
lets get this merged for DEVEL IBs so that @ianna can test and provide a fix for master |
Update DD4Hep to latest commit ae82afcac3986b62049c87fe3e96e2af790f75f8