Skip to content

use JULES update to read soil params namelist#43

Closed
JhanSrbinovsky wants to merge 3 commits into
mainfrom
42-update-access-am3-deployment
Closed

use JULES update to read soil params namelist#43
JhanSrbinovsky wants to merge 3 commits into
mainfrom
42-update-access-am3-deployment

Conversation

@JhanSrbinovsky

@JhanSrbinovsky JhanSrbinovsky commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

FYI @Whyborn - closes #42


🚀 The latest prerelease access-am3/pr43-5 at 32b8e2d is here: #43 (comment) 🚀

@JhanSrbinovsky JhanSrbinovsky linked an issue Jun 2, 2026 that may be closed by this pull request
@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr43-1 with commit e728364

🖥️ Gadi Deployment ❌

@JhanSrbinovsky

Copy link
Copy Markdown
Collaborator Author

@Whyborn - this is failing for reasons beyond my purview. My only change to spack.nml was to point to the JULES commit hash?

@Whyborn

Whyborn commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

That looks like a Gadi issue to me- I'll trigger it again

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr43-1 with commit e728364

🖥️ Gadi Deployment ❌

@JhanSrbinovsky

Copy link
Copy Markdown
Collaborator Author

@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

@Whyborn

Whyborn commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

!redeploy

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr43-4 with commit 8d7b110

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr43-3 with commit e728364

🖥️ Gadi Deployment ❌

@JhanSrbinovsky

JhanSrbinovsky commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator Author

@Whyborn - copilot is explaining the error as coming from an absent spack file that requires execute permission on vk83 to generate

@Whyborn

Whyborn commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

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.

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr43-5 with commit 32b8e2d

🖥️ Gadi Deployment ❌

@Whyborn

Whyborn commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

@CodeGat Still having no success with this- did you get a chance to take a look at it?

@Whyborn

Whyborn commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Something funky is going on- had some more failures which are just

Run rsync -e 'ssh -i /home/runner/.ssh/priv.key' \
ssh: connect to host *** port 22: Network is unreachable
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(232) [sender=3.2.7]
Error: Process completed with exit code 255.

@Whyborn

Whyborn commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

@JhanSrbinovsky I'm gonna open a new PR with this change to see if that fixes the problem

@CodeGat

CodeGat commented Jun 9, 2026

Copy link
Copy Markdown
Member

Those unreachable network errors seem to be transient gadi issues, I believe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

update ACCESS-AM3 deployment

3 participants