Update mom6 to its main repo. 20260828 commit

[jiandewang]

Commit Queue Requirements:

• This PR addresses a relevant WM issue (if not, create an issue).
• All subcomponent pull requests (if any) have been reviewed by their code managers.
• Run the full Intel+GNU RT suite (compared to current baselines), preferably on Ursa (Derecho or Hercules are acceptable alternatives). Exceptions: documentation-only PRs, CI-only PRs, etc.
  • Commit log file w/full results from RT suite run (if applicable).
  • Verify that test_changes.list indicates which tests, if any, are changed by this PR. Commit test_changes.list, even if it is empty.
• Transparency in the use of generative AI is required by NOAA policy. Was GenAI used in this work?
  • No.
  • Yes. [Generative AI tool (insert name, if any)] was used to assist with developing this code.
    • The code has been reviewed, edited, and validated by NWS staff. (Note: If the code has not yet been reviewed by NWS staff, leave unchecked, and OMD CMs will review as part of the PR review process.)
• Fill out all sections of this template.

---

Description:

MOM6 main was updated on 20260828 which is originally GFDL's 20260727 PR https://github.com/mom-ocean/MOM6/pull/1708. Need to sync to dev/emc and UFS

Commit Message:

* UFSWM - Update MOM6 to its main repo. 20260828 commit (GFDL's 20260727 PR)
  * MOM6 - Update MOM6 to its main repo. 20260828 commit (GFDL's 20260727 PR)

Priority:

• Critical Bugfix: Reason
• High: Reason
• Normal

Git Tracking

UFSWM:

• Closes update MOM6 to its maon repo. 20260828 commit #3343

Sub component Pull Requests:

• MOM6 - # Update mom6 to its main repo. 20260828 commit NOAA-EMC/MOM6#183

UFSWM Blocking Dependencies:

• Blocked by #
• None

Documentation:

• Documentation update required.
  • Relevant updates are included with this PR.
  • A WM issue has been opened to track the need for a documentation update; a person responsible for submitting the update has been assigned to the issue (link issue).
• Documentation update NOT required.
  • Explanation:

---

Changes

Regression Test Changes (Please commit test_changes.list):

• PR Adds New Tests/Baselines.
• PR Updates/Changes Baselines.
• No Baseline Changes.

Input data Changes:

• None.
• PR adds input data.
• PR changes existing input data.

Library Changes/Upgrades:

• Required
  • Library names w/versions:
  • Git Stack Issue (JCSDA/spack-stack#)
• No Updates

---

Testing Log:

• RDHPCS
  • Orion
  • Hercules
  • GaeaC6
  • Derecho
  • Ursa
• WCOSS2
  • Dogwood/Cactus
  • Acorn
• CI
• opnReqTest (complete task if unnecessary)

Testing Remarks:

[jiandewang]

@gspetro-NOAA I ran my branch on both hercules and URSA but only checked in hercules run log and test_change.list. There are several test cases (cpld and datm) that also need new baseline but they are excluded from hercules runs. For unknown reason my run on URSA failed to generate run log and test_change.list although all jobs were run

[gspetro-NOAA]

@gspetro-NOAA I ran my branch on both hercules and URSA but only checked in hercules run log and test_change.list. There are several test cases (cpld and datm) that also need new baseline but they are excluded from hercules runs. For unknown reason my run on URSA failed to generate run log and test_change.list although all jobs were run

I'll give it a try on my end today so that we can get the complete test_changes.list.

[jiandewang]

@gspetro-NOAA thanks for running on URSA to have the full change list.

[gspetro-NOAA]

Noting here that the failed check for an increase in warnings/remarks is due to an increase of 3 remark 10448 ifort deprecation. These can be ignored.

[jiandewang]

@gspetro-NOAA thanks for the explanation on warning flag, I was puzzled on that previously.

[gspetro-NOAA]

@gspetro-NOAA thanks for the explanation on warning flag, I was puzzled on that previously.

Np! Once we move to spack-stack 2.x, there should be no more remarks, but for now, we like to track them to make sure nothing unexpected comes up.

[gspetro-NOAA]

@jiandewang Please sync w/develop. We'd like to process this PR next. :)

[jiandewang]

@gspetro-NOAA do you think you can finishe all the platforms' run by the end of Firday ? I will be out of town from Saturday until next Thursday.

[jiandewang]

@gspetro-NOAA If you have write permission to my branch (revert MOM6 branch), then you can start my PR. @sanAkel can do the MOM6 merging.
I just sync-ed my branch.

[gspetro-NOAA]

@uturuncoglu If you have write permission to my branch (revert MOM6 branch), then you can start my PR. @sanAkel can do the MOM6 merging. I just sync-ed my branch.

@jiandewang I believe I have write permissions (having pushed the Ursa log), so when we get to that point in the process, I'm happy to revert .gitmodules and update the hash if you will be away. As long as @sanAkel can merge the MOM6 PR after we run the RTs, we should be okay. I expect the testing process may take a while anyway because Derecho is still out and won't be back from maintenance till tomorrow.

[jiandewang]

@gspetro-NOAA then you can start my PR and signal @sanAkel to merging MOM6 by the time.
@sanAkel please help me on this and make sure do NOT use squash merging.

[sanAkel]

@sanAkel please help me on this and make sure do NOT use squash merging.

@jiandewang please txt me when you need me to do ⬆️