Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Build based on 2026.06.03 run#7

Draft
blimlim wants to merge 3 commits into
mainfrom
2026.06.03-build
Draft

Build based on 2026.06.03 run#7
blimlim wants to merge 3 commits into
mainfrom
2026.06.03-build

Conversation

@blimlim

@blimlim blimlim commented Jun 23, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Collaborator

🚀 The latest prerelease access-esm3/pr7-8 at 178b083 is here: #7 (comment) 🚀

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-1 with commit d664271

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-1 with commit 8f6178b

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the 2026.06.03-build branch from 8f6178b to 879943d Compare June 23, 2026 07:49
@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-1 with commit 879943d

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the 2026.06.03-build branch from 879943d to 3ada675 Compare June 23, 2026 07:55
@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-1 with commit 3ada675

🖥️ Gadi Deployment ❌

@blimlim

blimlim commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-2 with commit 3ada675

🖥️ Gadi Deployment ❌

@blimlim

blimlim commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-3 with commit 3ada675

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-4 with commit efbc72e

🖥️ Gadi Deployment ❌

@blimlim

blimlim commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@anton-seaice anton-seaice marked this pull request as draft June 24, 2026 00:58
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-6 with commit efbc72e

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-5 with commit efbc72e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.000 as a Release (when merged).
  • pr7-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr7-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/1.1/spack in the access-esm3-pr7-5 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.06.004
  • 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.

@blimlim

blimlim commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-7 with commit efbc72e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.000 as a Release (when merged).
  • pr7-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr7-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/1.1/spack in the access-esm3-pr7-7 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.06.004
  • 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.

@blimlim blimlim force-pushed the 2026.06.03-build branch from efbc72e to 178b083 Compare June 24, 2026 10:07
@blimlim blimlim temporarily deployed to Gadi Prerelease June 24, 2026 10:09 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr7-8 with commit 178b083

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.000 as a Release (when merged).
  • pr7-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr7-8

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-esm3-pr7-8 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.06.004
  • 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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@blimlim @anton-seaice