Skip to content

Testing MOM5 build changes#191

Closed
dougiesquire wants to merge 2 commits intodev-1deg_jra55_ryffrom
test-mom5-cmake-1deg_jra55_ryf
Closed

Testing MOM5 build changes#191
dougiesquire wants to merge 2 commits intodev-1deg_jra55_ryffrom
test-mom5-cmake-1deg_jra55_ryf

Conversation

@dougiesquire
Copy link
Copy Markdown
Collaborator

This is a temporary PR for testing changes to the MOM5 build system

@dougiesquire
Copy link
Copy Markdown
Collaborator Author

!test repro

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 7, 2025

✅ The Bitwise Reproducibility Check Succeeded ✅

When comparing:

  • test-mom5-cmake-1deg_jra55_ryf (checksums created using commit 5e2e8e5), against
  • dev-1deg_jra55_ryf (checksums in commit fa65d53)
Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-om2-configs/5e2e8e50079a1b12252abe278b1844e9bfd2a6b0, and the test results at https://github.com/ACCESS-NRI/access-om2-configs/runs/41774105818.

The checksums generated by this !test command are found in the testing/checksum directory of https://github.com/ACCESS-NRI/access-om2-configs/actions/runs/14876226141/artifacts/3075723469.

The checksums compared against are found here https://github.com/ACCESS-NRI/access-om2-configs/tree/fa65d5360be0f4cf2563cbd082d833f0a17dced1/testing/checksum

@dougiesquire dougiesquire changed the title Use access-om2/pr103-2 Testing MOM5 build changes May 7, 2025
@dougiesquire
Copy link
Copy Markdown
Collaborator Author

!test repro

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 7, 2025

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

  • test-mom5-cmake-1deg_jra55_ryf (checksums created using commit 043c9f6), against
  • dev-1deg_jra55_ryf (checksums in commit fa65d53)
Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-om2-configs/043c9f67f8b6124765db62258132c6083f86455d, and the test results at https://github.com/ACCESS-NRI/access-om2-configs/runs/41775453180.

The checksums generated by this !test command are found in the testing/checksum directory of https://github.com/ACCESS-NRI/access-om2-configs/actions/runs/14876643336/artifacts/3075860213.

The checksums compared against are found here https://github.com/ACCESS-NRI/access-om2-configs/tree/fa65d5360be0f4cf2563cbd082d833f0a17dced1/testing/checksum

@dougiesquire
Copy link
Copy Markdown
Collaborator Author

dougiesquire commented May 7, 2025

@harshula, the two tests above show that moving from using FMS in the MOM5 repo to using external access-fms causes answers to change. Is that expected? The code should be the same right? So what is different?

@harshula
Copy link
Copy Markdown

harshula commented May 8, 2025

Hi @dougiesquire , The objective is to ensure ACCESS-NRI/FMS's mom5 branch is identical to the internal FMS version in MOM5, including compiler flags, etc. That should lead to access-fms functioning the same as the MOM5 internal FMS. You should definitely investigate why the answers are different.

@dougiesquire
Copy link
Copy Markdown
Collaborator Author

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.

2 participants