Skip to content

Builds with CABLE as a library#41

Open
Whyborn wants to merge 47 commits into
mainfrom
include-cable-as-library
Open

Builds with CABLE as a library#41
Whyborn wants to merge 47 commits into
mainfrom
include-cable-as-library

Conversation

@Whyborn

@Whyborn Whyborn commented May 27, 2026

Copy link
Copy Markdown
Collaborator

See title. The definitive build which includes CABLE as library instead of source code.


🚀 The latest prerelease access-am3/pr41-45 at 5dc46f6 is here: #41 (comment) 🚀

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-1 with commit ab7bc4e

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-2 with commit 5019882

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-3 with commit 1554923

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-4 with commit 4a9d4ef

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-5 with commit 3907cd9

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-6 with commit 674982a

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-7 with commit ad98300

🖥️ Gadi Deployment ❌

@Whyborn

Whyborn commented May 27, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

Added a comment to trigger redeploy.
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-8 with commit ad98300

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-9 with commit 71d5806

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-10 with commit b618baf

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-37 with commit 2875a87

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-38 with commit c8a107e

🖥️ Gadi Deployment ❌

@Whyborn Whyborn temporarily deployed to Gadi Prerelease June 17, 2026 10:05 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-39 with commit e878f6b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.002 as a Release (when merged).
  • pr41-39 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr41-39

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-pr41-39 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-am3 Prerelease pr41-40 with commit ae8f93a

🖥️ Gadi Deployment ❌

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

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-41 with commit d126d7a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.002 as a Release (when merged).
  • pr41-41 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr41-41

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-pr41-41 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

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

  • !bump major for feature releases
  • !bump minor for bugfixes

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-42 with commit b1246cf

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-42 with commit 6a40d64

🖥️ Gadi Deployment ❌

@Whyborn

Whyborn commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-44 with commit 98e0a70

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-43 with commit 6a40d64

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.07.000 as a Release (when merged).
  • pr41-43 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr41-43

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-pr41-43 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.

@Whyborn Whyborn deployed to Gadi Prerelease July 3, 2026 04:41 — with GitHub Actions Active
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr41-45 with commit 5dc46f6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.07.000 as a Release (when merged).
  • pr41-45 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr41-45

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-pr41-45 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