Skip to content

Conversation

@blimlim
Copy link
Collaborator

@blimlim blimlim commented Apr 22, 2025

PR for building OM3 libraries for CM3. Based on the new componentised build in 34-new-spack-components


🚀 The latest prerelease access-om3/pr79-12 at 80e44e7 is here: #79 (comment) 🚀

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-1 with commit a330486

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-2 with commit 4482b8b

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-3 with commit 05843af

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

!redeploy

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 23, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-6 with commit 264dfaf

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.x.0 as a Release (when merged).
  • pr79-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr79-6

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-pr79-6 environment.

Configuration Information

This Prerelease is deployed using:

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

@blimlim blimlim temporarily deployed to Gadi Prerelease April 23, 2025 03:42 — with GitHub Actions Inactive
@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-7 with commit 449d78b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.x.0 as a Release (when merged).
  • pr79-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr79-7

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-pr79-7 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.04.001
  • 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
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-8 with commit 823c8d8

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 23, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-9 with commit 823c8d8

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 23, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-10 with commit 823c8d8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.x.0 as a Release (when merged).
  • pr79-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr79-10

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-pr79-10 environment.

Configuration Information

This Prerelease is deployed using:

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

@blimlim blimlim temporarily deployed to Gadi Prerelease April 24, 2025 00:44 — with GitHub Actions Inactive
@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-11 with commit 6f59089

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.x.0 as a Release (when merged).
  • pr79-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

Configuration Information

This Prerelease is deployed using:

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

@blimlim blimlim temporarily deployed to Gadi Prerelease April 24, 2025 02:24 — with GitHub Actions Inactive
@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr79-12 with commit 80e44e7

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.x.0 as a Release (when merged).
  • pr79-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/pr79-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-pr79-12 environment.

Configuration Information

This Prerelease is deployed using:

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

@aidanheerdegen
Copy link
Member

Hey @blimlim. vk83 overran the inode quota, so we need to close some PRs to clean up the environments associated with the PRs.

You can re-open, or create a new PR as closing this one will clean up the intermediate deployments. Would that be ok?

@blimlim
Copy link
Collaborator Author

blimlim commented Jun 13, 2025

@CodeGat, there are currently some model runs going using pr79-12. All earlier deployments from this PR should be safe to delete though

@MartinDix
Copy link

@CodeGat Is there some way we can mark an older deployment as redundant and have it deleted w/o closing and re-opening.

@CodeGat
Copy link
Member

CodeGat commented Jun 13, 2025

Unfortunately, not yet - but see ACCESS-NRI/build-cd#277 for functionality that can do this.

Currently I can clean up the environments not needed in a PR with the service user, so you don't have to close the PR, but just tell me what environments are no longer needed :)

- parallelio
- fortranxml
- gcom
- openmpi
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- openmpi

Using the system openmpi module instead is better

esmf: '{name}/v8.7.0-{hash:7}'
netcdf-c: '{name}/4.9.2-{hash:7}'
netcdf-fortran: '{name}/4.6.1-{hash:7}'
gcom: '{name}/8.0-{hash:7}'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
gcom: '{name}/8.0-{hash:7}'
gcom: '{name}/8.0-{hash:7}'

You can rename this to something more convenient (e.g. which doesn't change with the hash) in draft PRs

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.

6 participants