Stewart X Addison
Stewart X Addison
> @sxa Can this be moved to https://github.com/AdoptOpenJDK/ci-jenkins-pipelines? Debatable - it's not purely a fix to the tags in there, it's also about making sure appropariate systems are available. I...
Related: https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1948 At the moment, only Azure systems are tagged for WiX (installer) jobs.
Note: The OpenJ9 builds (At least JDK8) are [restricted to these two machines](https://ci.adoptopenjdk.net/label/win2012&&mingw-cygwin&&build&&windows&&x64/) (not labelled to run on azure [unlike others](https://ci.adoptopenjdk.net/label/windows&&build&&win2012/))
Alibaba aarch64 builds are currently locked onto one machine (they [have to run on alibaba hardware](https://github.com/AdoptOpenJDK/openjdk-build/issues/2454#issuecomment-785763434) for now - we'll almost certainly have to allow both machines to be options...
### SUMMARY Many of these have now been resolved. From the top: - macos machine-specific entries in the pipelines have [now been removed](https://github.com/AdoptOpenJDK/ci-jenkins-pipelines/commit/74c3eaa29a6785c02c9dcd08d54d1d81994dc19d) (Corretto excepted) and run on [macos10.14](https://ci.adoptopenjdk.net/label/macos10.14&&build/) (2...
FYI @gdams @karianna @calderast
https://ci.adoptopenjdk.net/view/Failing%20Temurin%20jobs/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-alpine-linux-aarch64-temurin/47/console also froze today - both this one and the one in hte previous comment were using this boot JDK: ``` 21:06:21 BOOT JDK: openjdk version "11.0.15" 2022-04-19 21:06:21 BOOT...
I've had the build hang on other systems too (Docker containers on my HC4 and M1) although similar to the main build machines it doesn't happen 100% of the time,...
@AdamBrousseau Do you remember if we did see this one before and what the resolution might have been? Looks like it's running under a base `sh` or something instead of...
@AdamBrousseau Am I right in saying that you're currently building using CentOS7? We're still building on the CentOS6 container image which is why it's pointing to the separate openssl, so...