Skip to content

Ufs dev PR#251#1112

Merged
dustinswales merged 9 commits into
NCAR:mainfrom
dustinswales:ufs-dev-pr251
Feb 14, 2025
Merged

Ufs dev PR#251#1112
dustinswales merged 9 commits into
NCAR:mainfrom
dustinswales:ufs-dev-pr251

Conversation

@dustinswales
Copy link
Copy Markdown
Member

Contains changes from PR #251


- name: Checkout latest fv3atm
run: git clone https://github.com/NCAR/fv3atm.git
run: git clone https://github.com/NOAA-EMC/fv3atm.git
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Come to think of it, I'm not entirely sure that we need this file anymore since we're not maintaining our own branch of fv3atm? At least when this CI is run in the NCAR repo, it will fail henceforth I think. Wasn't the point of this test to sorta provide a "heads up" that the host (SCM) needs to change metadata somehow when physics PRs are introduced? It's trying to build the current fv3 with the PR branch physics. I guess that might still serve a purpose for the ufs/dev branch.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think what we want to do is:
In the NCAR:ccpp-physics we should have a CI test that runs prebuild using the SCM metadata.
In the UFS:ccpp-physics we should have a CI test that runs prebuild using the FV3 metadata.

Copy link
Copy Markdown
Collaborator

@grantfirl grantfirl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine as-is. Left a comment about the ci_fv3_ccpp_prebuild workflow.

@dustinswales
Copy link
Copy Markdown
Member Author

@grantfirl I opened an issue so we dont forget, #1113

@dustinswales dustinswales merged commit 3f601d7 into NCAR:main Feb 14, 2025
@dustinswales dustinswales deleted the ufs-dev-pr251 branch April 25, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants