-
Notifications
You must be signed in to change notification settings - Fork 7
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
UFS-dev PR#28 #83
UFS-dev PR#28 #83
Conversation
…nity#1523) * Convert all regression tests to use esmf-managed threading * update CMakeLists.txt * update rt.conf * Comment out unneeded steps in workflows/aux.yml * turn off control_c384 on cheyenne: all others passed Co-authored-by: Bin.Li <bin.li@noaa.gov> Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: jkbk2004 <jong.kim@noaa.gov>
…mmunity#1535) * allow option no updated sub-components * Run control_c384 and control_c384gdas tests on Gaea using TPN=18 Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: jkbk2004 <jong.kim@noaa.gov>
* clean up gitaction yml * Update build_test.yml, aux.yml
* fix fd_nems.yaml * cmeps restart will appear as different because field names changes * set TPN=18 on cheyenne: cpld_control_c192_p8, cpld_restart_c192_p8, hafs_global_multiple_4nests_atm Co-authored-by: Brian Curtis <Brian.Curtis@noaa.gov> Co-authored-by: jkbk2004 <jong.kim@noaa.gov>
* MYNNsfc uniform real kind Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: jkbk2004 <jong.kim@noaa.gov>
Automated RT Failure Notification |
Automated RT Failure Notification |
@grantfirl Looks like these tests are failing, as expected, when comparing to the mediator restart files: Cheyenne is down this week for maintenance, should we wait to run? or skip? |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@grantfirl Can you update the BL_DATE? (I see we made the classic mistake with the first BL_DATE of the year. Let's do 2023 for this one) |
I would say skip it because it has already been tested on Cheyenne in the ufs/dev branch. Hera should be good enough for our "verification" RTs for the main branch this time around. |
on-behalf-of @NCAR <dswales@ucar.edu>
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
Automated RT Failure Notification |
Identical to ufs-community#1522
Requires new baselines, but not for the CCPP code changes. The new baselines are required for ufs-community#1527. I think that this should only be for tests with WW3 active?