-
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
Trivial Changes to spack.yaml
Require Rebuild of Some Packages
#12
Comments
Double check if the Spack hash is the same or if it has changed. |
|
Both esmf and access-om3-nuopc have dependencies on parallelio (e.g. https://github.com/spack/spack/blob/c118c7733b9e20f079bb19b84b8ad60cacd2a673/var/spack/repos/builtin/packages/esmf/package.py#L91), so i'd guess its related to parallelio or one of its deps |
Another avenue is the |
Due to chats with spack devs, it might be useful to check the difference between the hashes with |
I don't know what this tells us :-)
|
Lots of noise ... But I have parallelio installed, do a concretise and it decides I need a new one (note
|
Currently, doing trivial modifications to the
spack.yaml
(seen most prominently in #5) require rebuildingparallelio
,esmf
and (therefore)access-om3-nuopc
. This is a bit of a time sink sinceesmf
can take upwards of 1/2 an hour.See the following runs, in which nothing was changed relating to the above packages: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/10987685371/job/30502929361?pr=5#step:8:767, https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/10985399681/job/30497188155#step:8:773.
Determine if the current
spack.packages.*.require
statements are not restrictive enough to prevent a rebuild - https://github.com/ACCESS-NRI/ACCESS-OM3/pull/5/files#diff-e8582e74fa156f4e5729a850e52b24f2fde2d815c2c9c360f88c4cf90db851abR10-R20Or maybe it's another problem?
The text was updated successfully, but these errors were encountered: