-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent build failures list #1450
Comments
jdk11-openj9/hotspot-windowsXL 13-12-2019 jdk11-windows-x32-hotspot 23-1-2020 jdk14-windows-x64-openj9 28-1-2020 jdk11u-windows-x64-hotspot 29-1-2020, 31-1-2020 jdk8u-windows-ALL-openj9 29-1-2020, 30-1-2020 jdk11u-windows-x64-openj9-windowsXL 30-1-2020, 31-1-2020
|
[EDIT by @sxa555: This is now resolved - also it's a test failure, not a build one ;-) ]
|
jdk11u-aix-ppc64-openj9 run 429 on build box 2
|
jdk13u/s390x/J9 - don't believe we've seen this on the older Marist systems
@lumpfish - got this today - 2020/01/22 [EDIT 2020/02/25 - This is https://github.com/adoptium/infrastructure/issues/1154] |
Windows JDK8u failure on JDK8/HotSpot builds as per #1236 (Recurred recently)
|
Got this today on build-osuosl-ppc64-aix-71-2
|
|
|
Occurred again on Count = 2 |
Occurred again on build-azure-win2008r2-x64-2 on job jdk8/windows_x64/HS 20/02/2020 Count = 2 -> RAISED adoptium/infrastructure#1169 |
aarch_64/aarch_64 java.rmi hash failures. Seen occasionally on j9 builds (first seen on
|
Seen a similar problem on a mac machine
|
|
@M-Davies The installer job failed on tha last build:
|
|
That one's ok - there was some additional maintenance happening at OSUOSL last night so that's not something that should recur |
JDK14 xLinux installer glitched last night - conncetion issue:
|
Hung build job, lost contact, network issue most likely:
|
jdk11u-aix-ppc64-hotspot
|
jdk8u-aix-ppc64-hotspot 20:15:27 build-osuosl-aix71-ppc64-2 was marked offline: Connection was broken: java.io.IOException: Unexpected EOF 20:15:27 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99) 20:15:27 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) 20:15:27 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) 20:15:27 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) |
jdk-aix-ppc64-hotspot 06:45:18 Cannot contact build-osuosl-aix71-ppc64-2: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@10cbe185:build-osuosl-aix71-ppc64-2": Remote call on build-osuosl-aix71-ppc64-2 failed. The channel is closing down or has closed down So it sounds like we lost the connection to build-osuosl-aix71-ppc64-2 mid-build again. That's at least four times in the past month (as per nightly triage). |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-openj9/892/console |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk16/job/jdk16-aix-ppc64-openj9/25/console |
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_linux/24379/console
|
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk/job/jdk-windows-aarch64-hotspot/27/console
API https://api.adoptopenjdk.net/v3/info/available_releases |
https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_sanity.openjdk_x86-64_windows_xl/12/console |
https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_sanity.openjdk_x86-64_windows_xl/14/console |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk16/job/jdk16-windows-x86-32-hotspot/34/console |
|
|
https://ci.adoptopenjdk.net/computer/build-osuosl-aix71-ppc64-1/ |
|
Notarize service timeout:
|
Node: build-osuosl-aix71-ppc64-1 |
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_mac/6416/console
|
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk/job/jdk-windows-aarch64-hotspot/46/console
|
|
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/sign_build/15065/console
node: https://ci.adoptopenjdk.net/computer/build-ibmcloud-win2012r2-x64-1/ |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-aix-ppc64-hotspot/941/console
|
Hung build: https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_sanity.functional_x86-64_windows/55/console
|
Me, @adam-thorpe and @andrew-m-leonard have been tracking sporadic build failures at ci.adoptopenjdk for triage purposes.
This list should now be made public so it can be contributed to by anyone observing the nightly builds.
Intermittent Nightly test list: adoptium/aqa-tests#1511
The text was updated successfully, but these errors were encountered: