-
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
Throw a clear exception if OutputModule SelectEvents refers to a non-existent Path or Process #44767
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44767/39985
|
A new Pull Request was created by @makortel for master. It involves the following packages:
@makortel, @smuzaffar, @Dr15Jones, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
@Dr15Jones Please review |
-1 Failed Tests: RelVals RelVals
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44767/40013
|
…existent Path or Process This was already the case for a non-existent Path of the present process. For non-existent Path of an earlier Process, or a non-existent Process, lead to a confusing exception message, and in some cases the job got stuck. An example of such stuck job was having an unrelated module in front of the OutputModule in the same EndPath.
Path::runNextWorkerAsync() pretty much assumes the runWorkerAsync() doesn't throw. runNextWorkerAsync() needs to schedule all eligible workers for the rest of the system to behave correctly.
332c1a4
to
27a4db4
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44767/40014
|
test parameters:
|
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b3c1e7/39180/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
@smuzaffar These extra workflows were not run as part of the tests of this PR (or as part of IBs AFAICT). Are the failures reported in the test summary above perhaps because some other PR used the same baseline, and those extra workflows were requested for the tests of that PR? |
Seems like this PR would be good to go. @Dr15Jones could you take a last look? |
yes looks like these extra workflows were requested by #44874 (comment). Bot should have ignore these workflow failures for this PR tests. I will look in to this |
+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, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
cms-sw/cms-bot#2221 should fix this for future PR tests |
PR description:
This was already the case for a non-existent Path of the present process. For non-existent Path of an earlier Process, or a non-existent Process, lead to a confusing exception message, and in some cases the job got stuck. An example of such stuck job was having an unrelated module in front of the OutputModule in the same EndPath.
Resolves #44743
Resolves #44744
Resolves cms-sw/framework-team#886
PR validation:
Added unit tests pass