Skip to content

34 New spack components w oneapi#84

Merged
anton-seaice merged 2 commits intomainfrom
34-clean
May 7, 2025
Merged

34 New spack components w oneapi#84
anton-seaice merged 2 commits intomainfrom
34-clean

Conversation

@anton-seaice
Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice commented May 6, 2025

Contributes to #34 and #41


🚀 The latest prerelease access-om3/pr84-3 at 2cbdd45 is here: #84 (comment) 🚀

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 6, 2025

🚀 Attempted to deploy access-om3 Prerelease pr84-1 with commit 447265f

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 6, 2025

🚀 Attempted to deploy access-om3 Prerelease pr84-2 with commit 447265f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.01.3 as a Release (when merged).
  • pr84-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr84-2

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-pr84-2 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.04.002
  • 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.

Copy link
Copy Markdown
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it's just a build system change, but to me this warrants a major version increment.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

Ok i've increment the version - noting no change to source code here, but oneapi will change answers. New version number is to make it easier to distinguish between intel-classic+single build compared to intel-onepi+spack-component based build

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 7, 2025

🚀 Attempted to deploy access-om3 Prerelease pr84-3 with commit 7e0ad49

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 7, 2025

🚀 Attempted to deploy access-om3 Prerelease pr84-3 with commit 2cbdd45

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.000 as a Release (when merged).
  • pr84-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.04.002
  • 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.

Copy link
Copy Markdown
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks @anton-seaice! The culmination of a lot of great work

@anton-seaice anton-seaice merged commit 2fe9598 into main May 7, 2025
10 checks passed
@anton-seaice anton-seaice deleted the 34-clean branch May 7, 2025 03:57
@anton-seaice anton-seaice temporarily deployed to Gadi Prerelease May 7, 2025 03:57 — with GitHub Actions Inactive
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.

3 participants