Skip to content

spack 0.22 repro tests#48

Draft
blimlim wants to merge 5 commits into
mainfrom
0.22-comparison
Draft

spack 0.22 repro tests#48
blimlim wants to merge 5 commits into
mainfrom
0.22-comparison

Conversation

@blimlim

@blimlim blimlim commented Mar 10, 2026

Copy link
Copy Markdown
Collaborator

Test builds to investigate reproducibility changes in the transition to spack 1.1


🚀 The latest prerelease access-esm1p5/pr48-5 at 19c4d27 is here: #48 (comment) 🚀

@blimlim blimlim temporarily deployed to Gadi Prerelease March 10, 2026 02:54 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p5 Prerelease pr48-1 with commit ae22cb0

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2024.12.1 as a Release (when merged).
  • pr48-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@blimlim blimlim temporarily deployed to Gadi Prerelease March 10, 2026 22:36 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p5 Prerelease pr48-2 with commit 8893bbd

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2024.12.1 as a Release (when merged).
  • pr48-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@blimlim blimlim temporarily deployed to Gadi Prerelease March 12, 2026 03:10 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p5 Prerelease pr48-3 with commit 00ae15b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2024.12.1 as a Release (when merged).
  • pr48-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@blimlim blimlim mentioned this pull request Mar 12, 2026
4 tasks
@blimlim blimlim temporarily deployed to Gadi Prerelease March 12, 2026 06:04 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p5 Prerelease pr48-4 with commit 9ad94f9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2024.12.1 as a Release (when merged).
  • pr48-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@blimlim blimlim deployed to Gadi Prerelease March 12, 2026 10:15 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p5 Prerelease pr48-5 with commit 19c4d27

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2024.12.1 as a Release (when merged).
  • pr48-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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