-
Notifications
You must be signed in to change notification settings - Fork 376
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
cime in maint-2.0 failed to work on anvil/chrysalis #6939
Comments
Are you sure your clone has the right submodules for maint-2.0? |
I would think so. A case created off it in the summer ran ok. Yesterday when trying to run some xml commands from its case_scripts directory, it reported failure. Creation of new case from the same code base reported the same error. The problem does not go away after forcing to deinit cime then reinitialize. I am trying a fresh clone of maint-2.0 now. |
No luck with a fresh clone of maint-2.0. My test script is: /home/ac.wlin/E3SM/Cases/testing/scripts/run.v2.LR.amip_0101_br2015.sh |
Try running one of the production tests that are passing in the nightlies. |
I tried reproducing this issue to no avail. The likeliest explanation is that some submods were not updated correctly? @wlin7 are you still seeing this issue? I can try to help |
Creation of a v3.LR.amip case (F20TR) on either chrysalis or anvil first got the following errors.
When replacing
cime_config = configparser.SafeConfigParser()
, withcime_config = configparser.ConfigParser()
it could go a little further but would then fail withDoes this mean we need to update the cime submodule for maint-2.0? prod_maint-2.0 tests on anvil has been fine, though.
The text was updated successfully, but these errors were encountered: