The instructions here in CONTRIBUTING.md fail, seemingly for a few reasons:
- The tests look for a
config_files.xml file in the parent directory of the CIME checkout. Doing export CIME_MODEL=cesm before testing resolves it, but...
- ...It then fails because it's looking for a
ccs_config/ directory in the CIME checkout's parent.
From the testing GitHub Workflow, it looks like the CIME tests need to be run within a model checkout with the ccs_config submodule loaded.
Even then, I got 57 failures and 28 skips.
Ideally, CIME would have its own ccs_config checkout within each CIME/data/config/$MODEL/ directory that could be used. Barring that, it would be good to update the instructions to say that the testing will only work within a model checkout.
If the latter solution is preferred, I can do it in a PR I'm working on now.
The instructions here in
CONTRIBUTING.mdfail, seemingly for a few reasons:config_files.xmlfile in the parent directory of the CIME checkout. Doingexport CIME_MODEL=cesmbefore testing resolves it, but...ccs_config/directory in the CIME checkout's parent.From the testing GitHub Workflow, it looks like the CIME tests need to be run within a model checkout with the
ccs_configsubmodule loaded.Even then, I got 57 failures and 28 skips.
Ideally, CIME would have its own
ccs_configcheckout within eachCIME/data/config/$MODEL/directory that could be used. Barring that, it would be good to update the instructions to say that the testing will only work within a model checkout.If the latter solution is preferred, I can do it in a PR I'm working on now.