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
Bugfix for cavern #25427
Bugfix for cavern #25427
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25427/7485 |
A new Pull Request was created by @slomeo (Sergio Lo Meo) for master. It involves the following packages: Geometry/CMSCommonData @civanch, @Dr15Jones, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
No, I have never used it for a production. When a (little) MC sample ,with Geo2018 (updated cavern and mb4shields) will be done, and it will be ok (now I have seen a too high background rate, perhaps because there was not a detailed cavern) I will request a central production. |
+1 |
Bugfix for cavern
Geometry 2018: Update Cavern and mb4shields for neutrons