-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
spack.yaml: depend on generic tracers Spack components #86
base: main
Are you sure you want to change the base?
Conversation
1789855
to
b4e6338
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-1 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
Awesome! |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-1 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
Hi @CodeGat , Same prerelease name for both deployments. |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-9 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there: https://forum.access-hive.org.au/t/csiro-access-nri-standup-minutes/3789/6 |
b4e6338
to
fcf18a3
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-10 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-11 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
NOTE Module
Module
|
fab81c8
to
706182c
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-12 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
706182c
to
8383e78
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-13 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-14 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
a2f87e8
to
e8c9ad3
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-15 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
Hey, due to ACCESS-NRI/build-cd#173 we have had to update the infrastructure in this repository, as well - see #90. We try and keep these kinds of updates to a minimum, and, starting from this one onwards, it will no longer be a hard requirement to update PR branches to incorporate infrastructure changes in order for the infrastructure to work - as you need to for this one. To update this PR to the new git pull
git rebase origin/main
git push --force to incorporate CI changes into the PR. Your PR may redeploy, but that is okay - it should be identical to the last deployment. Let me know if you have any questions or issues. |
e8c9ad3
to
05d5e7c
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86- where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
!redeploy |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86- where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
* Use tag dev_2024.08.14 instead of branch name * Set config to: "spack": "0.22", "spack-packages": "development",
05d5e7c
to
ae9c4f4
Compare
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-18 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
[Updated 15/12/2024: Provided link to deployment comment and provided more details] Hi @dougiesquire , @pearseb and @chrisb13 , If you want to test Spack-built ACCESS-OM2, with componentized generic-tracers, containing wombatlite-sinking, it's here: Verified:
|
What does this mean?
|
Use Pre-release |
🚀 Deploying access-om2 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om2/pr86-19 where the binaries shall be on your 🛠️ Using: spack DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
Hi @pearseb , Your latest changes should be in the following ACCESS-OM2 deployment: #86 (comment) |
Testing new infrastructure
Original PR: #82
🚀 The latest prerelease
access-om2/pr86-19
at 8239b13 is here: #86 (comment) 🚀