search

eclipse-openj9 / openj9

Eclipse OpenJ9: A Java Virtual Machine for OpenJDK that's optimized for small footprint, fast start-up, and high throughput. Builds on Eclipse OMR (https://github.com/eclipse/omr) and combines with the Extensions for OpenJDK for OpenJ9 repo.
Other
3.28k stars 721 forks source link

jdk_math_jre_0_FAILED Error: JDK not found #7515

Open JasonFengJ9 opened 4 years ago

JasonFengJ9 commented 4 years ago

Failure link

https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.openjdk_ppc64le_linux_Release/1/consoleFull

Failure output (captured from console output)

15:57:01  Error: JDK not found: /home/jenkins/jenkins-agent/workspace/Test_openjdk8_j9_sanity.openjdk_ppc64le_linux_Release/openjdkbinary/j2re-image
15:57:01  
15:57:01  jdk_math_jre_0_FAILED
pshipton commented 4 years ago

@smlambert mentioned: this test is there to verify that the jre builds at adopt ‘work’. But at OpenJ9 we don't archive the JRE build for jdk8, and I don't think we build it for jdk11+.

pshipton commented 4 years ago

@smlambert can we exclude this test in the OpenJ9 runs?

smlambert commented 4 years ago

We can exclude by implementation but not by CI server. At the moment if I exclude it, it will be excluded at AdoptOpenJDK also.

If you are building against nightly builds pulled from AdoptOpenJDK API, maybe should just additionally grab the JRE build at the same time.

Will think about ways to deal with it, other than the 2 mentioned above.

pshipton commented 4 years ago

I don't want to test against Adopt builds, but against the latest OpenJ9 build created at the OpenJ9 project.

smlambert commented 4 years ago

The short answer is that then OpenJ9 should archive the JRE that it builds, longer answer is we break that test out from the sanity set and run it as 'special' at Adopt, will need to think about this (and any complications it may introduce - fyi @sophia-guo).

pshipton commented 4 years ago

Archiving the JRE would consume more space, for something we don't really need. Moving stuff between the build machines and artifactory will take extra time, slowing down the builds. It's built for jdk8 but not sure it's already built for jdk11, adding it would slow down the builds a little.

smlambert commented 4 years ago

Yep, I am going to look at shifting it into special.openjdk target. Need to make an update to build scripts at Adopt to add that top-level target and make sure that we still pick up jre from upstream build etc, but it will mean it will no longer be present in the sanity.openjdk target that you now want to run at the OpenJ9 project (and so will not fail as it won't get run here).