-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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] evaluate all numeric parameters in tracker detector description #32371
[DD4hep] evaluate all numeric parameters in tracker detector description #32371
Conversation
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32371/20218
|
The tests are being triggered in jenkins.
|
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: Geometry/TrackerCommonData @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
Comparison is ready Comparison Summary:
|
+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 |
@silviodonato and @cvuosalo - which IB workflows are dd4hep based? Thanks |
please test workflow 11624.911, 11642.91 |
-1 CMSSW: CMSSW_11_3_X_2020-12-02-2300 I found follow errors while testing this PR Failed tests: RelVals
|
Hmm...
|
please test workflow 11624.911 |
+1 |
Comparison results are now available Comparison Summary:
|
@ianna usually we see the crash of the DD4HEP workflows only in the IB test. The PR tests are single thread and "often" run without errors. The good news is that we don't see the two failing workflows in |
@ianna As @silviodonato mentioned this seems to fix the IB issue for the two failing DD4hep workflows 11642.911 and 11624.911. Would you please backport #32371 and #32339 to 11_2_X? In 11_2_X IB, we still see the issues. |
ok, will do it asap |
PR description:
A follow up to the thread-safety issue reported by @Dr15Jones that was addressed in #32339:
all numeric constants should be evaluated.
Both step1 and step2 run to completion.
PR validation:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: