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

Skip to content

Initial Setup#2

Draft
anton-seaice wants to merge 13 commits into
mainfrom
initial_build
Draft

Initial Setup#2
anton-seaice wants to merge 13 commits into
mainfrom
initial_build

Conversation

@anton-seaice

@anton-seaice anton-seaice commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator

🚀 The latest prerelease access-esm3/pr2-17 at 06283c7 is here: #2 (comment) 🚀

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-1 with commit 7a9fea8

🖥️ Gadi Deployment ❌

@anton-seaice

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-2 with commit 7a9fea8

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-3 with commit b4dcdea

🖥️ Gadi Deployment ❌

@anton-seaice

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-4 with commit 5bc5076

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-5 with commit 5bc5076

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-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/pr2-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-pr2-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:

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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-6 with commit 2499f02

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-7 with commit 2499f02

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-8 with commit bf7c801

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-9 with commit 609c4fe

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr2-9

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-pr2-9 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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-10 with commit 6de3b2a

🖥️ Gadi Deployment ❌

@anton-seaice

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-11 with commit 6de3b2a

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-12 with commit 14c8489

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-13 with commit b9418f6

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr2-13

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-pr2-13 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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-14 with commit afe4772

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr2-14

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-pr2-14 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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-15 with commit af59531

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr2-15

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-pr2-15 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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-16 with commit 8e31fa5

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm3 Prerelease pr2-17 with commit 06283c7

🖥️ Gadi Deployment ✔️

Usage Instructions

``, defined in spack.yaml, will be deployed to `Gadi` as:

  • 2026.03.000 as a Release (when merged).
  • pr2-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr2-17

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-pr2-17 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.

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