Skip to content
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

SRW App doesn't build on PW NOAA Cloud Platforms #881

Closed
EdwardSnyder-NOAA opened this issue Aug 9, 2023 · 1 comment · Fixed by #901
Closed

SRW App doesn't build on PW NOAA Cloud Platforms #881

EdwardSnyder-NOAA opened this issue Aug 9, 2023 · 1 comment · Fixed by #901
Assignees
Labels
bug Something isn't working

Comments

@EdwardSnyder-NOAA
Copy link
Collaborator

Expected behavior

The SRW App should build on the NOAA Cloud platforms.

Current behavior

Currently, the SRW App cannot be built on the NOAA Cloud platforms as the modulefiles is using an outdated spack-stack.

Machines affected

PW NOAA Cloud platforms (i.e. Azure, AWS, and GCP)

Steps To Reproduce

Follow the document instructions to build the app. The error will occur when building the app.

Detailed Description of Fix (optional)

We were able to build the SRW App on the NOAA Cloud platforms using a newer spack-stack. See the noaa cloud module file here: /contrib/Edward.Snyder/rrfs-container-test/byhand/update/ufs-srweather-app/modulefiles.

Possible Implementation (optional)

Ensure the changes listed above work for the other two cloud platforms and create a PR to push these changes to develop branch.

@EdwardSnyder-NOAA EdwardSnyder-NOAA added the bug Something isn't working label Aug 9, 2023
@natalie-perlin
Copy link
Collaborator

Conda environments workflow_tools and regional_workflow_cmaq needed to be installed on Azure and GCP.
Installed now on all the NOAA cloud systems (AWS, GCP, Azure), and could be used for SRW tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants