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

Scheduled Repro Check Failed for Config release-1deg_jra55_iaf_bgc-3.0 #163

Closed
github-actions bot opened this issue Feb 5, 2025 · 7 comments · Fixed by #164
Closed

Scheduled Repro Check Failed for Config release-1deg_jra55_iaf_bgc-3.0 #163

github-actions bot opened this issue Feb 5, 2025 · 7 comments · Fixed by #164
Labels

Comments

@github-actions
Copy link

github-actions bot commented Feb 5, 2025

There was a failure of a monthly reproducibility check on ACCESS-NRI/access-om2-configs.

Model: access-om2, found here: https://github.com/ACCESS-NRI/access-om2
Config Repo: access-om2-configs, found here: https://github.com/ACCESS-NRI/access-om2-configs
Config Tag Tested for Reproducibility: release-1deg_jra55_iaf_bgc-3.0, found here:
Failed Run Log: https://github.com/ACCESS-NRI/access-om2-configs/actions/runs/13149937965
Experiment Location (Gadi): /scratch/tm70/repro-ci/experiments/access-om2-configs/release-1deg_jra55_iaf_bgc-3.0
Checksums created: In the testing/checksum directory of https://github.com/ACCESS-NRI/access-om2-configs/actions/runs/13149937965/artifacts/2538428662
Checksums compared against: https://github.com/ACCESS-NRI/access-om2-configs/tree/release-1deg_jra55_iaf_bgc-3.0/testing/checksum

Tagging @ACCESS-NRI/model-release

@CodeGat
Copy link
Member

CodeGat commented Feb 5, 2025

@aidanheerdegen, @dougiesquire, you may remember > 6 months ago, that the BGC configs all got an update from 2.0 to 3.0 to fix an error where the configs weren't reproducible with each other (see, for example #132). However, I've ran a dispatched test and discovered that they still do not reproduce. Is it related to #115?

@CodeGat
Copy link
Member

CodeGat commented Feb 5, 2025

I've looked at the above #115 and it seems that the configuration is using that latest version of ACCESS-OM2-BGC 2024.07.0, so the fix may not have worked: https://github.com/ACCESS-NRI/access-om2-configs/blob/release-1deg_jra55_iaf_bgc/config.yaml

@dougiesquire
Copy link
Collaborator

@CodeGat I don't think we fixed the restart reproducibility did we? The changes you're referring to above are fixing a coupling bug, but won't help with the reproducibility issue. So I think it makes sense that things still aren't reproducible.

I think (hope - I can't recall if I've checked this) the restart repro problem will be fixed when we move to the generic tracer BGC, but we're still finalising the build/spack logic for that and we haven't done the first release yet. I've reopened #112

@CodeGat
Copy link
Member

CodeGat commented Feb 6, 2025

Ohhh, I see...so all current *_bgc-* tags won't be restart reproducible..?

@dougiesquire
Copy link
Collaborator

That's my expectation

@CodeGat
Copy link
Member

CodeGat commented Feb 6, 2025

Alright, I'll remove the bgc-* tag from scheduled checking, then...thank you!

@dougiesquire
Copy link
Collaborator

I think (hope - I can't recall if I've checked this) the restart repro problem will be fixed when we move to the generic tracer BGC

Sadly not 😢. Though I intend to make it so!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants