In the suite of twelve CI tests that comprise the "Run MPAS Standalone (NOAA GSL tests)" CI test suite, the baseline forecasts for either the MPAS-Dev or ufs-community code are not running past the initialization time. This results in diag and history files only at the initialization time, with comparison script output also only at the initialization time.
Tracing the action logfiles back in time, this appears to have been introduced with #218 - the updated containerized CI + cleanup testing PR. The last merge prior to that for which there is a complete set of successfully completed tests is #210 - the MYNN surface-layer submodule PR - has the expected baseline output every 12 min to an hour.
There's no indication of the model crashing, and these CI tests pass, so I don't think it's an issue with the code used to run the baselines. In looking at the NOAA GSL CI test namelist.atmosphere.ncar files in the repository, it looks like they're set up to run for an hour, so I'm not immediately able to pinpoint the issue.
Assigning this to @dustinswales.
In the suite of twelve CI tests that comprise the "Run MPAS Standalone (NOAA GSL tests)" CI test suite, the baseline forecasts for either the MPAS-Dev or ufs-community code are not running past the initialization time. This results in diag and history files only at the initialization time, with comparison script output also only at the initialization time.
Tracing the action logfiles back in time, this appears to have been introduced with #218 - the updated containerized CI + cleanup testing PR. The last merge prior to that for which there is a complete set of successfully completed tests is #210 - the MYNN surface-layer submodule PR - has the expected baseline output every 12 min to an hour.
There's no indication of the model crashing, and these CI tests pass, so I don't think it's an issue with the code used to run the baselines. In looking at the NOAA GSL CI test namelist.atmosphere.ncar files in the repository, it looks like they're set up to run for an hour, so I'm not immediately able to pinpoint the issue.
Assigning this to @dustinswales.