Gregory Lemieux

@ekluzek @samsrabin Regression testing on derecho is complete and shows B4B results against `ctsm5.2.011` for all non-fates tests with one exception. The `RXCROPMATURITYSKIPGEN_Ld1097.f10_f10_mg37.IHistClm50BgcCrop.derecho_intel.clm-cropMonthOutput` test failed RUN again with the error...

Testing on izumi is is largely B4B with DIFFS only showing up for fates testmods as expected. That said there was a floating invalid exception caught due to a fates-side...

Status update: running `aux_clm` regression testing on `izumi` and `derecho`

Regression testing `aux_clm` on `izumi` against `ctsm5.0.12` is nearly complete. I'm just waiting on the 20 year crop testmod. All other expected tests are B4B aside from the expected DIFFs...

Regression testing of `aux_clm` on `derecho` finished up over night. All non-fates tests are B4B. Fates test DIFFs are expected as the update incorporates a number of other fates-side answer...

Status update: Running `e3sm_land_developer` tests against the current `master` commit on `perlmutter`.

@peterdschwartz regression testing using `e3sm_land_developer` on `perlmutter` against the `master` baseline is B4B for all expected tests. The DIFFs are all associated with fates tests and are expected. Results: `/pscratch/sd/g/glemieux/e3sm-tests/pr6353-eld-nanfix.fates.pm-cpu..E5b67e86c2a-F1982b003`

I wanted to highlight here this comment from #6235 that may be relevant for future work to address this: https://github.com/E3SM-Project/E3SM/pull/6235#issuecomment-2052266318

Thanks for taking a look at this. I'm running ifort 17.0.1 20161005. The error still seems to be persisting, unfortunately.