Update to oneAPI@2025.2.0 and OpenMPI@5.0.8

[manodeep]

---

🚀 The latest prerelease access-esm1p6/pr126-16 at 0db84af is here: #126 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-1 with commit 3103e68

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-1 with commit 3103e68

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-2 with commit 4410c88

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-3 with commit bf1f603

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• latest as a Release (when merged).
• pr126-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.08.000
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-4 with commit 8bfdef3

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• latest as a Release (when merged).
• pr126-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.08.000
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-5 with commit a4f7f4a

🖥️ Gadi Deployment ❌

[manodeep]

@CodeGat What does using oasis3-mct@upstream (which was merged today in pr313) require - my attempt failed here

[CodeGat]

Hey @manodeep - in order to use those changes, you'll need to update the spack-packages version in config/versions.json in this repo, since the deployment is using an older one. Change it to 2025.09.000 :)

[manodeep]

!redeploy

[manodeep]

Thanks @CodeGat 😄. I realise that even this version update might not be enough - the concretizer will likely bork with mom5, until @dougiesquire's PR is merged

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-6 with commit a4f7f4a

🖥️ Gadi Deployment ❌

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-7 with commit a4f7f4a

🖥️ Gadi Deployment ❌

[manodeep]

!redeploy

[manodeep]

(Jumped the gun a bit - hit redeploy before updating the spack-package version)

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-8 with commit c28760a

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• latest as a Release (when merged).
• pr126-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-8

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-8 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

!redeploy

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-10 with commit cf8744b

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-9 with commit c5b7aa4

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• latest as a Release (when merged).
• pr126-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-9

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-9 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-11 with commit 2132017

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• latest as a Release (when merged).
• pr126-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-11

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-11 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-12 with commit 856e88c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-13 with commit a0bd458

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.09.000 as a Release (when merged).
• pr126-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-13

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-13 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

Hmm - I merged in main to resolve the conflicts but I am pretty sure that is frowned upon. I probably needed to do a git pull before consolidating the commits (trying to apply the learnings from the git training at the workshop)

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-14 with commit 5c2e772

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.09.000 as a Release (when merged).
• pr126-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-14

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-14 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[manodeep]

@CodeGat That deployed really fast but I am not confident that it should have, especially because this line in the deployment logs is showing the @latest tag - but I was expecting the 2025.09.000 tag. I looked at the last deployment log and that's also using the @latest tag. May be I need to change something?

[manodeep]

Ahha - the issue was I was attempting to git rebase main rather than git rebase origin/main. The git log alias that Micael showed us at the workshop came in handy :)

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-15 with commit fc38019

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.09.000 as a Release (when merged).
• pr126-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-15

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-15 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-16 with commit f0a1bb5

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr126-16 with commit 0db84af

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.09.000 as a Release (when merged).
• pr126-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr126-16

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr126-16 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[dougiesquire]

LGTM - I assume you're planning to Squash and merge?

[manodeep]

@dougiesquire Since there is only one commit on the branch, I am fine with any of the three available options. What's the convention at ACCESS-NRI?

[dougiesquire]

I think squash and merge is appropriate here

[manodeep]

@blimlim also okay'ed merging this in - so in it goes :)

[CodeGat]

Hey all, just noting that the release (which deployed successfully), had an issue with the metadata upload. This will be fixed in v6 of the build-cd infrastructure, which is currently paused due to the large amount of open PRs. Hopefully around the end of the year there will be more PRs closed so we can have an easier time rebasing the open ones.

I'll add an entry to the release database manually 👍