Skip to content

Conversation

@blimlim
Copy link
Collaborator

@blimlim blimlim commented Nov 13, 2025

Continued tests for saving monthly mean output for UM river and CASA diagnostics. See here for background


🚀 The latest prerelease access-esm1p6/pr167-14 at 0e0a3d8 is here: #167 (comment) 🚀

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-1 with commit 88f2853

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the new-river+casa-tests branch from 88f2853 to 0408bd2 Compare November 13, 2025 02:31
@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-2 with commit b6ca899

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-2 with commit 079307b

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the new-river+casa-tests branch from 079307b to ba3ae55 Compare November 13, 2025 03:11
@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-3 with commit ba3ae55

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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:

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-esm1p6 Prerelease pr167-4 with commit 7c8bbd2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-4

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-esm1p6-pr167-4 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.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-5 with commit 1b04919

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-6 with commit d5e9f64

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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-esm1p6-pr167-6 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.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-7 with commit 883c6e7

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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-esm1p6-pr167-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:

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-esm1p6 Prerelease pr167-8 with commit 75c150c

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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:

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-esm1p6 Prerelease pr167-9 with commit 71699d9

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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.

@blimlim
Copy link
Collaborator Author

blimlim commented Nov 24, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-10 with commit 8f18f56

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Nov 24, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-11 with commit 940ea4a

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Nov 24, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-12 with commit 5fa39eb

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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-esm1p6-pr167-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.

@blimlim
Copy link
Collaborator Author

blimlim commented Nov 25, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-13 with commit cc69025

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.001 as a Release (when merged).
  • pr167-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr167-14 with commit 0e0a3d8

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.11.002 as a Release (when merged).
  • pr167-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr167-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/0.22/spack in the access-esm1p6-pr167-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.

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.

2 participants