Skip to content

Setup new spack build for CM3 libraries #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
blimlim wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Setup new spack build for CM3 libraries #150

blimlim wants to merge 6 commits into from

Conversation

@blimlim
Copy link
Collaborator

@blimlim blimlim commented Sep 16, 2025 •
edited by github-actions bot
Loading

Returning to the work started in #79 for getting the spack build of OM3 libraries working for CM3.

Currently focusing on cleaning everything up, and ideally we I'll get to:

  • All code versions using tags
  • Use the main branch of spack-packages
  • Use component versions consistent with specific OM3 releases

🚀 The latest prerelease access-om3/pr150-13 at 4f86438 is here: #150 (comment) 🚀

@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit 0b7a118

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from 0b7a118 to 3338059 Compare September 16, 2025 02:34
@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit 3338059

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from 3338059 to 05b4439 Compare September 16, 2025 02:48
@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit 05b4439

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit f3a06b1

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from f3a06b1 to 281886a Compare September 16, 2025 03:29
@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit 281886a

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from 281886a to f44264f Compare September 16, 2025 04:23
@github-actions
Copy link

github-actions bot commented Sep 16, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-2 with commit f44264f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@github-actions
Copy link

github-actions bot commented Sep 17, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-3 with commit 627818d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr150-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-om3-pr150-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 force-pushed the CM3-test-build-updates branch from 627818d to 186792c Compare September 17, 2025 02:16
@github-actions
Copy link

github-actions bot commented Sep 17, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-4 with commit 186792c

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr150-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-om3-pr150-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

github-actions bot commented Sep 18, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-5 with commit 501fe76

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from 501fe76 to 5ad0690 Compare September 18, 2025 01:01
@github-actions
Copy link

github-actions bot commented Sep 18, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-6 with commit 5ad0690

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr150-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-om3-pr150-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

github-actions bot commented Sep 18, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-7 with commit c4f91e8

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the CM3-test-build-updates branch from c4f91e8 to 8bc29cf Compare September 18, 2025 03:22
@github-actions
Copy link

github-actions bot commented Sep 18, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-8 with commit 8bc29cf

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Sep 19, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-9 with commit d2b89b6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr150-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-om3-pr150-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 blimlim force-pushed the CM3-test-build-updates branch from 9743a73 to 4f86438 Compare September 25, 2025 01:13
@github-actions
Copy link

github-actions bot commented Sep 25, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-10 with commit 9743a73

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Sep 25, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-1 with commit 4f86438

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Sep 25, 2025

!redeploy

@github-actions
Copy link

github-actions bot commented Sep 25, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-12 with commit 4f86438

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Sep 25, 2025

!redeploy

@github-actions
Copy link

github-actions bot commented Sep 25, 2025

🚀 Attempted to deploy access-om3 Prerelease pr150-13 with commit 4f86438

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr150-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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