forked from ESMCI/cime
-
Notifications
You must be signed in to change notification settings - Fork 13
CIME Development Guide
goldy edited this page Aug 4, 2016
·
11 revisions
Requests to merge changes into the CIME trunk are done by submitting a pull request on github.
Prior to integration and accepting a pull request:
-
CIME unit tests need to be run:
- Fortran: From the top-level directory in cime, follow the instructions in README.unit_testing (currently only works out-of-the-box on yellowstone)
- TODO - perl (andre, shollenberger)
- TODO - python (andre, ???)
-
CIME standalone tests need to be run from the CIME/scripts directory:
./create_test \
--xml-compiler intel \
--xml-category prealpha \
--xml-testlist ../driver_cpl/cime_config/testdefs/testlist_drv.xml \
--test-root /some/path/tests-cime-27dbd045 --test-id 27dbd045
To check results:
cd /some/path/tests-cime-27dbd045
./cs.status
- For small changes, run the -component drv tests for the intel compiler on Yellowstone as well as the nag and pgi compilers on Hobart.
- For significant changes, the CESM prealpha tests should also be run on Yellowstone (intel).