Skip to content
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

Windows/JDK8/J9 production 0.11.0 builds currently failing #725

Closed
sxa opened this issue Nov 9, 2018 · 16 comments
Closed

Windows/JDK8/J9 production 0.11.0 builds currently failing #725

sxa opened this issue Nov 9, 2018 · 16 comments
Assignees
Labels
bug Issues that are problems in the code as reported by the community openj9 Issues that are enhancements or bugs raised against the OpenJ9 group

Comments

@sxa
Copy link
Member

sxa commented Nov 9, 2018

Reason unclear but the resulting java execution is resulting in:

The application has failed to startt because it's side-by-side configuration is incorrect. Please see the application event log or use the command line sxstrace.exe tool for more detail

In the build log when trying to execute it we get:

Finished building OpenJDK for target 'images'
'/tmp/tmp.kJ76onEiGA/workspace/./build//src/build/windows-x86_64-normal-server-release/images/j2sdk-image' found
/cygdrive/c/Users/jenkins/workspace/SXA-jdk8_j9_win64_build/sbin/build.sh: line 353: /tmp/tmp.kJ76onEiGA/workspace/./build//src/build/windows-x86_64-normal-server-release/images/j2sdk-image/bin/java: Accessing a corrupted shared library
 Error executing 'java' does not exist in '/tmp/tmp.kJ76onEiGA/workspace/./build//src/build/windows-x86_64-normal-server-release/images/j2sdk-image'.
Relocating workspace from /tmp/tmp.kJ76onEiGA to /cygdrive/c/Users/jenkins/workspace/SXA-jdk8_j9_win64_build/workspace
Data at: /cygdrive/c/Users/jenkins/workspace/SXA-jdk8_j9_win64_build/workspace
@sxa sxa added bug Issues that are problems in the code as reported by the community openj9 Issues that are enhancements or bugs raised against the OpenJ9 group labels Nov 9, 2018
@sxa sxa self-assigned this Nov 9, 2018
@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Related issues: #719 #690
Related PRs: #726
Doing test builds under https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/3/console for now

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Worked ok at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/3 with

TAG: jdk8u192-b12
configure_args: --with-milestone=fcs
BRANCH: openj9-0.11

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Failed at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/4 with

TAG: jdk8u192-b12_openj9-0.11.0
configure_args: --with-milestone=fcs
BRANCH: openj9-0.11

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Passed with tag portion of filename replaced with the new string at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/5 with just ADDITIONAL_FILENAME_TAG set

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Failed at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/6 with

TAG: jdk8u192-b12_openj9-0.11.0
configure_args:
BRANCH: openj9-0.11

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Passed at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/7 with

TAG: jdk8u192-b12
configure_args: --with-milestone=fcs
BRANCH: openj9-0.11
ADDITIONAL_FILENAME_TAG: jdk8u192-b12_openj9-0.11.0

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Failed at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/8 with

TAG: jdk8u192-b12_openj9-0.11.0
configure_args: --with-milestone=fcs
BRANCH: openj9-0.11
ADDITIONAL_FILENAME_TAG: jdk8u192-b12_openj9-0.11.0

@sxa
Copy link
Member Author

sxa commented Nov 9, 2018

Testing at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/9 with

TAG: 
configure_args: --with-milestone=fcs
BRANCH: openj9-0.11
ADDITIONAL_FILENAME_TAG: jdk8u192-b12_openj9-0.11.0

@sxa sxa changed the title Windows/JDK8/J9 builds currently failing Windows/JDK8/J9 production 0.11.0 builds currently failing Nov 12, 2018
@sxa
Copy link
Member Author

sxa commented Nov 12, 2018

Parameter has been added to expose ADDITIONAL_FILENAME_TAG which we will use for the production builds #732

@sxa sxa closed this as completed Nov 12, 2018
@sxa
Copy link
Member Author

sxa commented Nov 13, 2018

Re-opening as I'm still hitting issues:


configure: Found Microsoft Visual Studio 2010
configure: Rewriting VS_ENV_CMD to "/cygdrive/c/progra~2/micros~4.0/vc/bin/amd64/vcvars64.bat"
configure: Trying to extract Visual Studio environment variables
Setting environment for using Microsoft Visual Studio 2010 x64 tools.
configure: Setting extracted environment variables
/cygdrive/c/cygwin64/tmp/tmp.UD5miaHsOB/workspace/build/src/build/windows-x86_64-normal-server-release/vs-env/set-vs-env.sh: line 2: syntax error near unexpected token `('
/cygdrive/c/cygwin64/tmp/tmp.UD5miaHsOB/workspace/build/src/build/windows-x86_64-normal-server-release/vs-env/set-vs-env.sh: line 2: `VS_INCLUDE="c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE;c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\ATLMFC\INCLUDE;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\include;C:\Program Files\Debugging Tools for Windows (x64)\sdk\inc; "'
configure exiting with result code 2
Relocating workspace from /tmp/tmp.UD5miaHsOB to /cygdrive/c/Users/jenkins/workspace/SXA-jdk8_j9_win64_build/workspace
Data at: /cygdrive/c/Users/jenkins/workspace/SXA-jdk8_j9_win64_build/workspace
total 8.0K

This appears to only be the case when the TAG variable is set, but if it's not set the java -version output gets populated with a datestamp (See build at https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-jdk8_j9_win64_build/9) ... But build 11 was ok

@sxa
Copy link
Member Author

sxa commented Nov 13, 2018

11 was built with the pre branch of my openjdk-build repo. 14 will be built with what was hopefully the same as 9

@sxa sxa reopened this Nov 13, 2018
@sxa
Copy link
Member Author

sxa commented Nov 13, 2018

I think the variable issue with the ) was down to having the jenkins agent started as the wrong user. Now passing that point running as jenkins

@sxa
Copy link
Member Author

sxa commented Jan 25, 2019

Since we've shipped it I'm going with this now having finished successfully. Closing

@sxa sxa closed this as completed Jan 25, 2019
@sxa
Copy link
Member Author

sxa commented Jan 30, 2019

Still issues - currently the builds are producing filenames of OpenJDK8U-jdk_x64_mac_openj9_jdk8u202-b08_openj9-0.12.0_8u202b08.tar.gz when building with:

TAG: jdk8u202-b08
configure_args: 
BRANCH: openj9-0.12
ADDITIONAL_FILENAME_TAG: jdk8u202-b08_openj9-0.12.0

@sxa sxa reopened this Jan 30, 2019
@karianna karianna added this to the January 2019 milestone Jan 30, 2019
@M-Davies
Copy link

@sxa Can this be closed?

@sxa
Copy link
Member Author

sxa commented May 18, 2020

The build pipelines are now passing, so I'd say yes

@sxa sxa closed this as completed May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are problems in the code as reported by the community openj9 Issues that are enhancements or bugs raised against the OpenJ9 group
Projects
None yet
Development

No branches or pull requests

3 participants