Update GNUPGHOME variable more broadly #3630
Conversation
github-actions
bot
added
the
alpine-linux
|
I can confirm this work, see https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk22/job/jdk22-evaluation-linux-riscv64-temurin/19/console for details. |
It's an issue on linux-riscv64 valuation pipelines for jdk23. See https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk23/job/jdk23-evaluation-linux-riscv64-temurin/2/console for example.
There was a problem hiding this comment.
PR checks have failed so I'm going to put a block on this, but as an FYI JDK22 (required as a boot JDK for 23) has now been published at https://github.com/adoptium/temurin22-binaries/releases/tag/jdk-22%2B33-ea-beta so the 23 build should be able to find it.
|
The PR checks have failed either on "No space left of device" or "No such file or directory" for files which are not in |
|
The build failures (I'm ignoring the smoke test one for now which is three or of space one) seem related to the gpg key. I didn't think we had any issues with that at the moment. @andrew-m-leonard can you cast an eye over this and see if this failure is expected at the moment? I'll remove my block for now since if Andrew is ok I'm happy for it to go in 😀 |
|
Re-running your original failing job at https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk23/job/jdk23-evaluation-linux-riscv64-temurin/12/console now that this PR has been merged. |
|
I'm a little unclear on how we've ended up with a which is distinct from But it's failing trying to clone https://github.com/adoptium/jdk23.git I've kicked off the above test again using the |
It's an issue on linux-riscv64 valuation pipelines for jdk23. See https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk23/job/jdk23-evaluation-linux-riscv64-temurin/2/console for example.
Should normally fix #3378