Skip to content

Testing recipe

Rosie Fisher edited this page Mar 19, 2025 · 2 revisions

Testing recipe

Once you've checked out the correct versions of all components, do the following: Under /cluster/work/username/noresm make a new folder for the set of tests you are doing with a meaningful name, like:

mkdir /cluster/work/username/noresm/TEST_somefeature_no1

Then go in the CTSM_root/cime/scripts/ folder and do:

./create_test --xml-category aux_clm_noresm --xml-machine betzy -p nnprojectnumber -r /cluster/work/username/noresm/TEST_somefeature_no1 --parallel-jobs 6

That will run all the clm-tests and chuck the results in the /cluster/work/username/noresm/TEST_somefeature_no1 folder

Once the tests have run you can go in that folder and there should be something there called cs.status You can run the whole thing to get a massive report, or you can do

./cs.status -f
./cs.status -x CTSM_root/cime_config/testdefs/ExpectedTestFails.xml 

or combine them, to get just the failed tests, or to omit the expected failed tests

Also in the /cluster/work/username/noresm/TEST_somefeature_no1 folder are the outputs from each tests, so you can look at outputs and read logs for each of them in there.

Clone this wiki locally