use JULES update to read soil params namelist#43
Conversation
|
🚀 Attempted to deploy 🖥️
|
|
@Whyborn - this is failing for reasons beyond my purview. My only change to spack.nml was to point to the JULES commit hash? |
|
That looks like a Gadi issue to me- I'll trigger it again |
|
🚀 Attempted to deploy 🖥️
|
|
@Whyborn - it seems there is a spack lock on the build at: /g/data/vk83/prerelease/apps/spack/1.1/restricted/ukmo/release/.spack-db/lock IDK if it is as simple as removing the lock but I dont have write permission on vk83 anyway |
|
!redeploy |
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
@Whyborn - copilot is explaining the error as coming from an absent spack file that requires execute permission on vk83 to generate |
|
Definitely shouldn't be the case, the build is done with a service user that does have permissions on vk83. I'll have a chat to @CodeGat about it, but won't be much movement on this over the next 2 days, we have the NRI retreat. |
|
🚀 Attempted to deploy 🖥️
|
|
@CodeGat Still having no success with this- did you get a chance to take a look at it? |
|
Something funky is going on- had some more failures which are just |
|
@JhanSrbinovsky I'm gonna open a new PR with this change to see if that fixes the problem |
|
Those unreachable network errors seem to be transient gadi issues, I believe |
FYI @Whyborn - closes #42
🚀 The latest prerelease
access-am3/pr43-5at 32b8e2d is here: #43 (comment) 🚀