-
Notifications
You must be signed in to change notification settings - Fork 728
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
sanity.openjdk native_sanity #7521
Comments
@llxia @smlambert what do we need to do to setup these tests properly? |
These tests use the openjdk native test libs (built and available from AdoptOpenJDK, related adoptium/temurin-build#1251). Presumably those native test images are also being built at OpenJ9 (if the builds scripts run 'make all'), just not being archived anywhere for retrieval. |
The build does run |
Yes, please note the difference between the test natives created as part of building openjdk test directory used by openjdk tests (part of the whole clone clone make story), versus the variety of openj9 test natives that are historically built and used by functional tests. openjdk vs functional - 2 completely different groups of test material |
@jdekonin we need to include the openjdk directory in the native-test-libs.tar.gz |
Where/how are these natives located/generated in JDK8? |
jdk8 is different than jdk10+ builds in jdk8 'make all' would build test native libs, in jdk10+ explicit make target to build them 'make test-image' and new requirement to use cmdline option -nativetestpath to run them I presume details are in the various readme's off of http://openjdk.java.net/groups/build/ and by looking at the makefiles in the extensions repo |
@pshipton - in the immediate term, I was thinking to shift this jdk_native_sanity target to the 'special' level, along with jdk_math_jre target (discussed in different issue) so neither test target would be executed in the OpenJ9 (which only runs 'sanity' and 'extended' levels). Longer term, it is still a good idea for this to be resolved by building the openjdk test images at OpenJ9. |
Note we didn't get failures in jdk8 testing, the failures were in jdk11. It seems the problem is we need to run |
ok, for now I will just move the jre testing to special unless I hear differently in this issue |
The build jobs at openj9 are creating the jdk test lib if I am not mistaken:
However they are not being added into the native-test-libs.gz.tar archive, it is only grabbing the functional native test lib: |
* rename native-test-libs.tar.gz -> test-images.tar.gz to match what openjdk test framework is looking for * eclipse-openj9#7521 * [skip ci] Signed-off-by: Joe deKoning <[email protected]>
I believe this is fixed and can be closed? |
Should be. |
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_ppc64le_linux_Nightly/1
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_x86-64_mac_Nightly/1
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_s390x_linux_Nightly/1
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_ppc64_aix_Nightly/1
Use -nativepath to specify the location of native code
The text was updated successfully, but these errors were encountered: