-
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
Improve behavior after exception in begin/end global lumi #44840
Improve behavior after exception in begin/end global lumi #44840
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44840/40088
|
A new Pull Request was created by @wddgit for master. It involves the following packages:
@cmsbuild, @Dr15Jones, @makortel, @smuzaffar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable threading |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ba46e8/39075/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
daed9f8
to
8794d0e
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44840/40110
|
please test I pushed a commit and that combined with the responses above should resolve all the comments. Let me know if there are any more. |
Pull request #44840 was updated. @makortel, @smuzaffar, @Dr15Jones can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ba46e8/39125/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
+core |
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. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Improve the behavior of the Framework after global begin/end lumi exceptions. This is the second in a series of PRs where we plan to make the behavior after exceptions more consistent in all the begin/end transitions. The first PR handled stream begin/end lumi exceptions (see #44624). The comments at the head of that PR state the design for this behavior we are implementing.
The intent is that nothing in the output will change if there are not any exceptions.
This work was motivated by discussions related to Issues #43831 and #42501.
This PR also adds some new exception context information for exceptions occurring in service functions related to begin/end transitions.
PR validation:
An existing unit test covering exceptions in different transitions is extended to cover the most salient cases. Additional manual testing of many various cases was also done. Existing unit tests pass.