Skip to content

Update shumlib to use the head of the upstream.#45

Open
Whyborn wants to merge 3 commits into
mainfrom
move-to-head-of-upstream-shumlib
Open

Update shumlib to use the head of the upstream.#45
Whyborn wants to merge 3 commits into
mainfrom
move-to-head-of-upstream-shumlib

Conversation

@Whyborn

@Whyborn Whyborn commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Move to the head of shumlib upstream, in preparation for merging in the extrapolation fix identified here (thanks @paocorrales). We want to be up to date with the upstream before we apply the fix, and attempt to merge the fix into said upstream.


🚀 The latest prerelease access-am3/pr45-3 at db40ac7 is here: #45 (comment) 🚀

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr45-1 with commit 4bfaae1

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr45-2 with commit b27dffb

🖥️ Gadi Deployment ❌

@Whyborn Whyborn temporarily deployed to Gadi Prerelease June 9, 2026 01:53 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr45-3 with commit db40ac7

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.000 as a Release (when merged).
  • pr45-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr45-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/1.1/spack in the access-am3-pr45-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 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.05.005
  • access-nri/spack-config version 2026.05.004

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.

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.

1 participant