-
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
Fix bug related to cmsRun exit code with FileReadError #43579
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43579/38221
|
A new Pull Request was created by @wddgit (W. David Dagenhart) for master. It involves the following packages:
@smuzaffar, @cmsbuild, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
abort test |
a64555c
to
e5504fb
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43579/38224
|
Pull request #43579 was updated. @cmsbuild, @Dr15Jones, @smuzaffar, @makortel can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2f2728/36519/summary.html Comparison SummarySummary:
|
+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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Fix bug related to cmsRun exit code with FileReadError exception. It was returning 8001 instead of 8021. See Issue #42179 for more discussion. Note this bug was introduced in 12_3_X and this PR will need to be backported to cover active releases since then.
PR validation:
An existing unit test was extended to check the exit code after a FileReadError. In the schema evolution tests there is a file that will exhibit such an error and I used that. Otherwise, it is pretty hard to create such a file intentionally (silver lining of an unrelated 13_0_0 ROOT bug). Note that I don't intend to backport the unit test part because the schema evolution unit test it depends on is relatively new.