-
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
Exit code 8028 not being reported anymore #42040
Comments
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @makortel Matti Kortelainen. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
Thanks Matti!
|
The problematic piece of code is here cmssw/IOPool/Input/src/RootInputFileSequence.cc Lines 253 to 275 in c06c3ee
The We should also add a test to ensure this behavior. |
@wddgit is looking into this. https://github.com/cms-sw/cmssw/blob/master/FWCore/Services/test/test_sitelocalconfig.sh has tests that set a custom I think it would be good to have one test with one Here is an example how to check the exit code is as expected cmssw/IOPool/Input/test/TestPoolInput.sh Lines 9 to 14 in c34a318
|
PR #42249 should fix this on the master branch. |
Hi Stephan. When I try to backport the fix to 12_4_X, the new unit test starts to fail. It worked successfully for 13_3_X, 13_2_X, 13_1_X, 13_0_X, 12_6_X and 12_5_X. The last one Matti asked me to backport to was 12_4_X... At first glance this appears to be a failure with the unit test not the bug fix. I am investigating, but if you understand what is going on that would be helpful. For some reason it is trying 2 file paths with the first catalog instead of only one. And the second one gives a fallback error. Probably something in the catalog code changed from 12_4_X to 12_5_X.
|
Hallo Dave,
|
I had to modify the unit test a little for 12_4_X. I think the difference was it uses the older code. But the bug fix is the same as in all the other backports. All the backports are submitted now. 6 PRs waiting for approval. |
Correct, the Rucio catalog code has not yet been backported to 12_4_X, and therefore, strictly speaking, the tests of the 12_4_X backport (#42396) are incorrect. Given that the Rucio catalog was planned to be backported to 12_4_X, redoing the tests of #42396 for TFC seems wasted effort. @stlammel @nhduongvn Would it be feasible to resume backporting the Rucio catalog (#37278 (comment))? |
Yes, I can backport new developments to 12_4_X sometime next week so that we can include the support of chaining as well. |
For the 12_4_X bug fix backport only, we decided to go ahead with the backport of the bug fix without the unit test. The plan is to add the unit test either in the 12_4_X Rucio backport (when that is ready) or as a separate PR after that. Then we can use the same unit test in 12_4_X as we are using in master and the other bug fix backports. Given that we are already running the unit test in master and we've manually verified the bug fix works in 12_4_X, that seems good enough. |
Backports of the fixes have been merged |
+core |
This issue is fully signed and ready to be closed. |
It was noticed in https://cms-talk.web.cern.ch/t/not-possible-to-open-2022g-data-files-crab-or-manual-xroot/25738/8 that CMSSW_13_0_5_patch2 reported exit code 8020 (
FileOpenError
) after a fallback file open fails instead of the expected 8028 (FallbackFileOpenError
). Digging in history revealed the #28911 had a mistake (that I overlooked in the review) by throwingFileOpenError
also when a fallback file open fails.#28911 was merged in 11_1_0_pre8, so the fix needs to be backported to
The text was updated successfully, but these errors were encountered: