Temurin-build: JDK-Next Windows Installer Failing

Created on 27 Apr 2020  路  26Comments  路  Source: adoptium/temurin-build

Platform:
jdk_next-windows

Architecture:
x64-hotspot

~https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk/job/jdk-windows-x64-hotspot JDK next has tests disabled for x64-Windows on nightlies but seems to be trying to run them anyway.~ This is an installer failure as per https://github.com/AdoptOpenJDK/openjdk-build/issues/1712#issuecomment-621933568

Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
Running test: false
[Pipeline] parallel
[Pipeline] { (Branch: false)
[Pipeline] stage
[Pipeline] { (false)
[Pipeline] library
Only using first definition of library openjdk-jenkins-helper
[Pipeline] echo
Requested test job that does not exist or is disabled: Test_openjdk15_hs_false_x86-64_windows
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // parallel
[Pipeline] node
Running on Jenkins in /home/jenkins/.jenkins/workspace/build-scripts/jobs/jdk/jdk-windows-x64-hotspot
[Pipeline] {
[Pipeline] stage
[Pipeline] { (installer)
[Pipeline] build (Building build-scripts 禄 release 禄 create_installer_windows)
Scheduling project: build-scripts 禄 release 禄 create_installer_windows
Starting building: build-scripts 禄 release 禄 create_installer_windows #3884
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
Execution error: null
[Pipeline] End of Pipeline
Finished: FAILURE
bug

All 26 comments

FYI @andrew-m-leonard

Build today seems alright. It failed, but was due to the sign_build job this time

For some reason, buildConfig.TEST_LIST is set to false at this point, and still tries to run tests. Adding a check to ensure only valid tests are ran, should be sufficient to fix this issue.

The PR is a valid workaround, but should we not fix the root cause?

In the interest of allowing the builds to run, this PR will work for now. Fixing the root cause would be preferable and will be the next step

Landed the PR, reopening this issue to find root cause

Looking at the passing mac builds, they also have this error but move past this point, implying that it's not the test list thats the problem

Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] echo
Running test: false
[Pipeline] parallel
[Pipeline] { (Branch: false)
[Pipeline] stage
[Pipeline] { (false)
[Pipeline] library
Only using first definition of library openjdk-jenkins-helper
[Pipeline] echo
Requested test job that does not exist or is disabled: Test_openjdk15_hs_false_x86-64_mac

The issue instead could be due to the installer failing.

Execution error: null

Will raise in slack.

Ref https://adoptopenjdk.slack.com/archives/C09NW3L2J/p1588261040169800?thread_ts=1588260983.169700&cid=C09NW3L2J, this is an installer failure. Nothing to do with the testlists pulling in the wrong information. My mistake.

Build step 'Execute Windows batch command' marked build as failure
Archiving artifacts
[Slack Notifications] found #3883 as previous completed, non-aborted build
[Slack Notifications] will send OnEveryFailureNotification because build matches and user preferences allow it
Finished: FAILURE

Sidenote, I really hope that https://github.com/AdoptOpenJDK/openjdk-build/pull/1717 works as I keep misreading the console logs! :/

Ok so it's the installer that's failing, is anyone currently triaging the installer failure jobs?

@andrew-m-leonard ?

The latest failure, https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/3947/console (for those who have perms to see). I think the failure seems to stem from this bit in the console output.

First .\SourceDir\OpenJDK15\hotspot\x64\jdk-15.0.0 not exists
Second .\SourceDir\OpenJDK15\hotspot\x64\jdk-15+21 not exists
Third .\SourceDir\OpenJDK15\hotspot\x64\jdk-15.0.0+21 not exists
SOURCE Dir not found / failed

which corresponds to this in the Build.OpenJDK_generic.cmd script of the Installer repo. In passing builds, at least one of these directories exists

Was this page helpful?
0 / 5 - 0 ratings