-
Notifications
You must be signed in to change notification settings - Fork 301
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
Add some tests to the test suites Chris Fischer runs #276
Comments
@ekluzek I'm assigning this to you. I think you've done some of it, but some items may need to be reviewed. |
@ekluzek - I noticed that some of the Specific tests that I see in
I'm adding a checklist item to this effect in the original, top-level comment. |
OK, I've gone through this and am bringing this in on the release-branch. prealpha/prebeta tests also have a aux_clm test, and aux_cime_baselines have a closely matched prealpha test. |
Added prebeta tests for: SSP, Fates, drydep, Qian, fire-emis, cam6lndTuning, ciso, BgcSpinup, PET, DAE, waccm-deck 1&2 degree, and some more gnu on hobart and cheyenne. Add SSP, PEM, BgcSpinup, SMS_D_Ld3.f10_f10_musgs.I1850Clm50BgcCrop, and ERP_P180x2_D_Ld5.f19_g17.I2000Clm50Sp for prealpha. |
See also #800 |
In a discussion with @mvertens , @jedwards4b , @fischer-ncar @cacraigucar, we decided that Chris will not regularly run the
aux_clm
test suite. Instead, we will add some tests to the prealpha and prebeta test suites if we feel there are additional tests that could catch cime issues that currently slip through the cracks.In addition, we decided that there should be a new test category,
aux_cime_baselines
. This will likely be a subset of the prealpha test suite. This should be a small test suite (ideally no more than 3 or 4 tests defined by each component) whose purpose is to make sure that changes in cime have not changed answers relative to baselines for important configurations - i.e., that no answer changes have accidentally crept into cime. We want to keep this test suite small (even if that means not quite complete coverage) because it will be run frequently. It should be sufficient to have a few short SMS tests on a single machine/compiler (cheyenne_intel
) - maybe covering a few different time periods and/or datm modes?Review prealpha tests defined by ctsm for completeness. @ekluzek have you already done this recently? Also, make sure that all prealpha tests are also in aux_clm (or have very similar tests in aux_clm).
Review prebeta tests defined by ctsm for completeness. @ekluzek have you already done this recently? Also, make sure that all prebeta tests are also in aux_clm (or have very similar tests in aux_clm).
Define a new set of tests in ctsm's testlist xml file -
aux_cime_baselines
- as per the above notes.Make sure that all
aux_cime_baselines
tests have similar tests inprealpha
(see Add some tests to the test suites Chris Fischer runs #276 (comment))cc @ekluzek @bandre-ucar
The text was updated successfully, but these errors were encountered: