UFS-dev PR#54#93
Conversation
* "merge RRFS-SD to the community repository" * "include the MYNN-EDMF update PR ufs-community#1636" * add new control_p8_mynn test to exercise the FV3_GFS_v17_p8_mynn suite * change some variables to environment-controlled in cpld_control.nml.IN; add satmedmf=T for export_cpl() in default_vars.sh; add satmedmf=T for tests that use cpld_control.nml.IN, but not export_cpl * add new smoke_dir_fdb_coef to rrfs test namelist Co-authored-by: joeolson42 <Joseph.B.Olson@noaa.gov> Co-authored-by: Haiqin.Li <Haiqin.Li@noaa.gov> Co-authored-by: Grant Firl <grant.firl@noaa.gov>
|
Automated RT Failure Notification |
This comment was marked as outdated.
This comment was marked as outdated.
|
Expected test failures for Hera-Intel: Expected failures for Hera-Gnu: Also, any tests that use the smoke/dust code. |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
@dustinswales The Cheyenne/intel compilation errors look strange, but I think it is just a space thing. I tried to clear out the rt_* data in /glade/scratch/dswales/FV3_RT and got permissions error. I can write/delete a new file/dir there, though. I wonder if doing the setfacl default command being done after the rt_* data was already written means that I can't remove them after the fact? Regardless, I'll need you to delete them, since I think we're out of space. I'll try to delete again after I run cheyenne-intel-BL there to verify my hypothesis. I'm going to go ahead and do create new BLs though since the RTs that did finish look like correct failures. |
|
@grantfirl I just cleaned up the space on Cheyenne. |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
|
@dustinswales Please approve when you get a chance. This should be ready to merge. |
3 participants
Identical to ufs-community#1658