ESMCI / ESMCI/cime

cime_developer needs to work and be regularly tested

Open
#5,015 6 comments 0 reactions 3 assignees Claimed by @billsacks View on GitHub
CRITICAL
Dominant language
Python
Stars
174
Forks
225
Avg merge
1d 16h
Merged PRs (30d)
14

Description

cime_developer was the standard full CIME system test for years. I just tried running it on my machine and most of the cases in this suite do not work. The mpi-serial test failed due to some missing env modules on my machine, but the others look like they would fail for everyone:

Several tests failed with:
` ERROR: Bad STOP_N: 9 (0 coupling intervals)`

MCC failed with:
```
File "/home/jgfouca/E3SM-clean/cime/CIME/SystemTests/mcc.py", line 18, in __init__
if ninst > 1:
TypeError: '>' not supported between instances of 'NoneType' and 'int'
```

IRT failed with:
```
ERROR: (shr_pcdf_readwrite) ERROR: IRT_N2_Vmct_Ln9.f19_g16.A.mappy_gnu.20260722_121323_wsqzmj.dice_0002.r.0001-01-01-16200.nc doesnt exist
```

NCK failed with:
`ERROR: (factor_moab_comp) cannot get factors drv2mdl`

PRE tests failed with:
```
Computing partition using RCB method for 64 processors...
ERROR: (prep_ocn_merge_moab) error in getting i2x_om array
```

There will be several steps needed to fully address this situation:

- [ ] CI will need to have a "long" test action that runs cime_developer or test_sys_full_system.py for both CESM and E3SM
- [ ] We will need to fix some of the problems above for the suite to actually pass
- [ ] We may need to agree on a couple basic, small grids that both CESM and E3SM will agree to support

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.