-
Notifications
You must be signed in to change notification settings - Fork 248
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
Cloud Dependencies for Regression Testing #1667
Cloud Dependencies for Regression Testing #1667
Conversation
@ulmononian Can you monitor with this PR in terms of spack stack maintenance strategy on PW clouds? We need to keep a consistency of machine names between weather model and srw as well. |
@SadeghTabas-NOAA Here's the draft cloud PR I was referring to previously. @ulmononian Sadegh was able to build new permanent Spack-Stack modules on Parallel Works AWS, for our use in this PR. Would you be able to assist us in doing the same for GCP and Azure? |
Automated RT Failure Notification |
on-behalf-of @ufs-community <jong.kim@noaa.gov>
on-behalf-of @ufs-community <ecc.platform@noaa.gov>
on-behalf-of @ufs-community <jong.kim@noaa.gov>
on-behalf-of @ufs-community <ecc.platform@noaa.gov>
Automated RT Failure Notification |
Didn't wait for Acorn. they passed though. Can't push to this any more. |
@BrianCurtis-NOAA I could hold my approval until acorn log come. This pr is only for pw-cloud feature. Sanity check can be enough for validation with other machines. @FernandoAndrade-NOAA FYI |
I see '-B' option was added back to nccmp. Was that intended? |
@DusanJovic-NOAA Yes, the Cheyenne admin installed nccmp/1.9.1.0 on the HPC, which has the -B option. |
Excellent. Thank you. |
Description
Add PR to support running the UFS WM Regression Test script on the three NOAA Cloud HPCs (GCP, Azure and AWS).
To run the UFS WM Regression Test suite on the NOAA Cloud platforms, RT related scripts, module and fv3 slurm job files need to be updated with Cloud platform related dependencies and variables.
Following these updates, rt.sh should run any test from the rt.conf suite.
Top of commit queue on: TBD
Input data additions/changes
Anticipated changes to regression tests:
Subcomponents involved:
Combined with PR's (If Applicable):
Commit Queue Checklist:
Linked PR's and Issues:
Testing Day Checklist:
Testing Log (for CM's):