Mac x64 "sign_verification" hangs running `jimage` on non-orka macos12 nodes
Ref: https://ci.adoptium.net/job/build-scripts/job/release/job/sign_verification/2687/
+ cp -r unpacked/jdk/jdk-24.0.1+9/Contents jdk_cp
[Pipeline] echo
Expanding JMODS and 'modules' under unpacked/jdk
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
+ set -eu
+ set +x
Expanding compressed image file unpacked/jdk/jdk-24.0.1+9/Contents/Home/lib/modules
Does not seem to hang if run on Orka node
Looks like the jimage command is hanging even when run with no parameters:
test-macincloud-macos1201-x64-2:sign_verification jenkins$ jdk_cp/Contents/Home/bin/jimage
@andrew-m-leonard Do you have a note of where this hung? Would it have been the macincloud macos12 systems?
@andrew-m-leonard Do you have a note of where this hung? Would it have been the macincloud macos12 systems?
Yes I believe so, which is why we added "&&orka" to the label to avoid those, and I don't think we've had a hang since
ref: https://github.com/adoptium/ci-jenkins-pipelines/blob/bf4b9bff0d4230459f53946835476b0fa7dc5028/pipelines/build/common/openjdk_build_pipeline.groovy#L1131
Noting for future reference that I approved that "under duress" as locking to a single provider is not ideal https://github.com/adoptium/ci-jenkins-pipelines/pull/1228#pullrequestreview-2881804609
Noting also for anyone picking this up that - since it has now been been hardcoded into the pipelines - temporarily adding the orka label to a macincloud system would likely be the only way to allow this to be replicated other than using an alternate branch in the job.