Conversation
b8af046 to
ce772d8
Compare
|
Note, this has been rebased to incorporate features from |
…common api-v2 tag
6f44909 to
35e2de0
Compare
…re target, remove gcc-runtime requirement
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
!update-configs |
|
🔧 Opening Model Configuration PRs in Configurations RequestedConfigurations requested from profile
Pull Requests OpenedThe following PRs were opened: More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/21973699640 |
|
Hmm. Those all failed the |
|
Thats normal @CodeGat The repro failure was :
see payu-org/payu#688 ? |
|
I've rerun those and unfortunately all those configs fail repro_historical tests 😔 I'll redraft this one for now...it should be equivalent! |
|
Good with me. Thanks for tracking all this down @anton-seaice |
|
Shall I commit to this PR @CodeGat ? I think we should do a new release & deployment for this |
|
Yea go for it - don't forget to update the version number! |
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
Soo speedy ! |
|
!update-configs |
|
🔧 Opening/Updating Model Configuration PRs in Configurations RequestedConfigurations requested from profile
Pull Requests Opened/UpdatedThe following PRs were opened/updated: More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/22379702097 |
|
Weird bug @CodeGat - the update-configs command has tried to use pr163-5, but we are only up to pr163-4 ? |
|
Ready to go, see answers are maintained: ACCESS-NRI/access-om3-configs#1161 (comment) |
|
🚀 Attempted to deploy 🖥️
|
dougiesquire
left a comment
There was a problem hiding this comment.
LGTM, thanks @CodeGat and @anton-seaice!
References issue ACCESS-NRI/build-cd#313 and PR ACCESS-NRI/build-cd#326
References rollout issue ACCESS-NRI/build-cd#328
References project Spack `0.22` to `1.0` Migration
Note
This infrastructure update created a new Release, but it maintained reproducibility with the current
mainImportant
This PR is a major update to the deployment infrastructure. See below for the prerequisites for this repository to be able to merge this PR.
Important
This major version change marks the end of major infrastructure updates for deployments to
spack < 1.0.If you want to deploy to instances of
spack < 1.0, you must usebuild-cd < v8.If you want to deploy to instances of
spack >= 1.0, you must usebuild-cd >= v8.Background
We are moving on up to
spack v1! This update to spack contains many bug fixes, optimisations and new features that can be incorporated intobuild-cd.This update also contains changes that make
spack v0.Xincompatible with thisbuild-cd v8update - the most prominent one being the splitting of spacks core codebase from it's builtin spack-packages repo. This means that for provenance, one to keep track of bothbuiltinspack-packages and our own, renamedaccess-spack-packages.build-cdwill centrally control the version of builtinspack-packagesfor a given instance, andconfig/versions.jsonsspack-packageskey is renamed toaccess-spack-packages.As noted earlier, this major version of
build-cdcan only supportspack v1, due tospack v1-specific commands in the infrastructure. If you still want to deploy tospack v0.X, you will need to changebuild-cdtov7, and update theconfig/versions.jsonfile/spack.yaml.Features
Prerequisites for Merging
build-cdentrypoints (this PR!)config/versions.jsonwith new inputs (also this PR!)spack v1🚀 The latest prerelease
access-om3/pr163-6at 7af308f is here: #163 (comment) 🚀