-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
backport extended exception for geant4/vecgeom tracking #37381
backport extended exception for geant4/vecgeom tracking #37381
Conversation
A new Pull Request was created by @civanch (Vladimir Ivantchenko) for CMSSW_12_2_X. It involves the following packages:
@cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
This PR backports a subset of #36717, and its fixes in #37216 A comment about the previous decision of not backporting those two PRs in 12_2_X was written in #36780 (comment) |
I have tried to extend the description. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-966e5b/23452/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_4_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
urgent |
+1 |
PR description:
Backport extended handling of Geant4/VecGeom exceptions from the master in order to address #37373. Here only files are backported from #36717 and #37216 with modifications of code for exceptions. Geant4 trace of exceptions expected with the new Geant4 11.0 is not considered.
PR validation:
private