Closed jasonb5 closed 7 months ago
Looks like there is still a "maximum recursion depth exceeded in comparison" error introduced by #4572 and is still specific to E3SM.
2024-02-07 23:04:52: ERROR: Bad xpath search term './/entry[@id='CIMEROOT']', error: maximum recursion depth exceeded in comparison
Exception from case_test: ERROR: Bad xpath search term './/entry[@id='CIMEROOT']', error: maximum recursion depth exceeded in comparison
The recursion error was caused by CIME.XML.env_batch._submit_single_job
not correctly handling the dry_run
argument for tests.
E3SM system testing exposed the issue during it's pre-run provenance capture where it calls case.preview_run
which calls _submit_single_job
with the dry_run
argument. Since the dry_run
argument was not handled for tests it would cause _submit_single_job
to submit the job again, causing the recursion error.
case.preview
call for E3SMTest suite: Test baseline: Test namelist changes: Test status: [bit for bit, roundoff, climate changing]
Fixes [CIME Github issue #] User interface changes? Update gh-pages html (Y/N)?: