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

2024.03.1 and 2024.06.0 releases are broken #13

Open
5 tasks done
dougiesquire opened this issue Jul 3, 2024 · 1 comment
Open
5 tasks done

2024.03.1 and 2024.06.0 releases are broken #13

dougiesquire opened this issue Jul 3, 2024 · 1 comment

Comments

@dougiesquire
Copy link
Collaborator

dougiesquire commented Jul 3, 2024

access-om2-bgc 2024.03.1 and access-om2-bgc 2024.06.0 are built with hdf5 1.14.3 which contains a bug that prevents ACCESS-OM2-BGC from running.

The issue is fixed in hdf5 1.14.4, but this version is not yet available in the spack package.

What's the right way forward here? Revert to hdf5 1.14.2 for now?

Note, this issue also affects one ACCESS-OM2 release - see ACCESS-NRI/ACCESS-OM2#74

Tasks

  • Remove access-om2-bgc 2024.03.1 as a Release (but keep the tag for transparency)
  • Remove access-om2-bgc 2024.06.0 as a Release (but keep the tag for transparency)
  • Create the (first!) backport/2024.03 branch, which is where the 2024.03.* (namely, 2024.03.2) tags will live, since there is a 2024.06.0 in front in the history.
  • Link PR for 2024.03.2 that addresses the above
  • Link PR for 2024.06.1 that addresses the above (can be main branch)
@CodeGat
Copy link
Contributor

CodeGat commented Jul 17, 2024

Note: We have released a ACCESS-OM2-BGC 2024.07.0 that contains just the MOM5 WOMBAT bug fix. The above can still be done.

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

No branches or pull requests

2 participants