oneapi@2025.0.4

[anton-seaice]

---

🚀 The latest prerelease access-om3/pr37-17 at f274b72 is here: #37 (comment) 🚀

[github-actions]

🚀 Deploying access-om3 2024.09.0 as prerelease pr37-1 with commit 2c4fdcf

Details and usage instructions

This access-om3 model will be deployed as:

• 2024.09.0 as a Release (when merged).
• pr37-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-1

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr37-1 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

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

If this is not what was expected, commit changes to config/versions.json.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-3 with commit 1a3b79e

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-3 with commit 1a3b79e

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-3 with commit 156c2d9

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-3 with commit e8abbb3

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-4 with commit 404b22e

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-4 with commit cb8b4fc

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-5 with commit 525cac6

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-5 with commit 27a5129

🖥️ Gadi Deployment ❌

[anton-seaice]

!redeploy

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-5 with commit 27a5129

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.1 as a Release (when merged).
• pr37-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-5

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-om3-pr37-5 environment.

Configuration Information

This Prerelease is deployed using:

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

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

[anton-seaice]

!redeploy

[anton-seaice]

(I set compiler to f"{compiler}" incase the % char was having a weird impact

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-11 with commit 35de926

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-12 with commit 787220d

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.1 as a Release (when merged).
• pr37-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-12

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-om3-pr37-12 environment.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 202-om3-nuopc+oneapi
• access-nri/spack-config version 2025.02.2

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

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-13 with commit 688e46a

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.2 as a Release (when merged).
• pr37-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-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-om3-pr37-13 environment.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 202-om3-nuopc+oneapi
• access-nri/spack-config version 2025.02.2

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

[anton-seaice]

!redeploy

(ACCESS-NRI/access-spack-packages@b1d98e6) removed cflags for esmf

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-14 with commit 688e46a

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.2 as a Release (when merged).
• pr37-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-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-om3-pr37-14 environment.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 202-om3-nuopc+oneapi
• access-nri/spack-config version 2025.02.2

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

[anton-seaice]

(I moved build_type to this file, and unset fp-model in the package)

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-15 with commit 79cb702

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.2 as a Release (when merged).
• pr37-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-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-om3-pr37-15 environment.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 202-om3-nuopc+oneapi
• access-nri/spack-config version 2025.02.2

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

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-16 with commit 3c23be6

🖥️ Gadi Deployment ❌

[anton-seaice]

!redeploy

(force RelWithDebInfo to be set the same as it used to be)

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-16 with commit 3c23be6

🖥️ Gadi Deployment ❌

[anton-seaice]

!redeploy

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-17 with commit f274b72

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr37-17 with commit f274b72

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

• 2025.01.2 as a Release (when merged).
• pr37-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr37-17

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-om3-pr37-17 environment.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 202-om3-nuopc+oneapi
• access-nri/spack-config version 2025.02.2

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

[anton-seaice]

Learnings: there's no need to set any build flags specially for oneapi