Skip to content

Conversation

@mnlevy1981
Copy link
Collaborator

Instead of running git submodule update --init --recursive and then relying on git fleximod test to make sure the submodules match what git fleximod expects, the test now runs git fleximod update and then uses git diff --exit-code to see if that's different than what git submodules expect. This is a "six of one, half dozen of the other" type change, but is consistent with what was discussed at a CSEG meeting.

I also cleaned up some white space.

Instead of running "git submodule update --init --recursive" and then relying
on "git fleximod test" to make sure the submodules match what git fleximod
expects, the test now runs "git fleximod update" and then uses "git diff
--exit-code" to see if that's different than what git submodules expect. This
is a "six of one, half dozen of the other" type change, but is consistent with
what was discussed at a CSEG meeting.

I also cleaned up some white space.
@mnlevy1981
Copy link
Collaborator Author

This currently keeps MOM6 at dev/ncar_250128 -- there's an ongoing discussion about whether we should use this updated tag (what was expected in cesm3_0_beta05) or drop back to dev/ncar_241122b (what was actually in beta05). After a decision has been made, I'll either mark this as ready for review or push one more commit with the change to the older tag and then mark it as ready for review.

@mnlevy1981
Copy link
Collaborator Author

@alperaltuntas should we close this? I think the existing test works well enough, and there's also the testing done in ESCOMP/CESM so it's probably not worth figuring out whatever I was trying to change here

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.

1 participant