Skip to content

Test build for CM3 changes to spack#32

Closed
anton-seaice wants to merge 19 commits into
mainfrom
test_cm3_spack_build_changes
Closed

Test build for CM3 changes to spack#32
anton-seaice wants to merge 19 commits into
mainfrom
test_cm3_spack_build_changes

Conversation

@anton-seaice

@anton-seaice anton-seaice commented May 19, 2026

Copy link
Copy Markdown
Collaborator

Test for ACCESS-NRI/access-spack-packages#410


🚀 The latest prerelease access-ram3/pr32-2 at 92405bd is here: #32 (comment) 🚀

@anton-seaice
anton-seaice changed the base branch from infra-update-v8 to main May 19, 2026 04:50
@anton-seaice
anton-seaice changed the base branch from main to infra-update-v8 May 19, 2026 04:51
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-ram3 Prerelease pr32-1 with commit a11b1e2

🖥️ Gadi Deployment ❌

@anton-seaice anton-seaice changed the title Update versions.json Test build for CM3 changes to spack May 19, 2026
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-ram3 Prerelease pr32-1 with commit 545b23b

🖥️ Gadi Deployment ✔️

Usage Instructions

access-ram3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.000 as a Release (when merged).
  • pr32-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-ram3/pr32-1

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/1.1/spack in the access-ram3-pr32-1 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:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@CodeGat
CodeGat force-pushed the infra-update-v8 branch from 493efbb to ca28649 Compare May 21, 2026 23:09
Base automatically changed from infra-update-v8 to main May 22, 2026 00:13
@CodeGat

CodeGat commented May 22, 2026

Copy link
Copy Markdown
Member

Gday @anton-seaice, the infra-update-v8 branch is now merged into main. If this PR has any more work needed, it'll have to be rebased - happy to help out with this!

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-ram3 Prerelease pr32-2 with commit 92405bd

🖥️ Gadi Deployment ✔️

Usage Instructions

access-ram3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.000 as a Release (when merged).
  • pr32-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-ram3/pr32-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/1.1/spack in the access-ram3-pr32-2 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:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@anton-seaice
anton-seaice deleted the test_cm3_spack_build_changes branch June 19, 2026 01:05
@anton-seaice
anton-seaice deployed to Gadi Prerelease June 19, 2026 01:05 — with GitHub Actions Active
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