-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
Installer build break #1683
Comments
Seems to be across all platforms and JDK versions, including next |
It looks like you are talking about jobs such as https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-ppc64le-hotspot/486/console |
It looks like the associated test jobs, such as https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_sanity.openjdk_ppc64le_linux/202/console failed though
|
Correct. My assumption is that it's the installer as the build itself completed successfully. Looking at some of the test failures, it looks like there might have been a network glitch last night on the jtreg side so it could be that the job died halfway through due to the internet dropping out https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_j9_sanity.openjdk_x86-64_linux/206/console |
Ah. Just seen you commented the exact same thing 😄 |
@sxa Could we kick off a new respin of nightlies to verify it was just a glitch? |
JDK11 pipeline is still running at the moment, so I was going to kick off 8 but they haven't failed in the same way ... The tests appear to have been ok on there |
it's not the installer jobs. this was broken by #1668 |
The above revert does not appear to have fully resolved this as https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-linux-ppc64le-hotspot/517/consoleFull still shows the failure despite the above revert going in |
Regarding this issue, the builds look a lot happier this morning. Thanks for the help on this |
For reference, the revert of #1687 resolved this |
Installer jobs are causing the nightly builds to fail. I don't have the perms to see or diagnose the problems.
May also be due to a network glitch that has also killed some of the testing jobs #1683 (comment)
The text was updated successfully, but these errors were encountered: