-
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] Tests Cleanup and 2021 Production Scenario Update #30093
Conversation
@slomeo - FYI |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30093/15833
|
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: Configuration/Geometry @perrotta, @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: cd144a0 CMSSW: CMSSW_11_2_X_2020-06-02-2300 I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test DD4hepGeometryTestDriver had ERRORS |
Comparison job queued. |
@ianna A lot of different changes are made in this PR. I think you have fixed some bugs or enhanced functionality in |
+1 |
+1 |
+upgrade |
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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
For the record, additional details about this PR: The PR is done in preparation for DDCMS code migration to DD4hep repository. All DPG related tests were moved under the DPG subsystems along with their automated execution. Many of the subsystems, for which the DPG are responsible, did not have it implemented before. The tests used a private 2021 scenario that was more up to date then the production one. I’ve updated the 2021 production scenario and modified all test configurations to use it. The first was removed. This fixed Sergio’s problem with an offset in the comparison: the modified YE thickness was not propagated to the scenario he was using. |
PR description:
PR validation:
unit tests and integration tests run by default
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: