-
Notifications
You must be signed in to change notification settings - Fork 720
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
JDK22 cmdLineTester_loadLibraryTests_0_FAILED #18975
Comments
Grinder failed 100% |
|
JDK21 x86-64_windows passed
|
JDK 8/11/17/21/22 personal build JDK8 x86-64_windows cmdLineTester_loadLibraryTests_0_PASSED( JDK22 x86-64_windows cmdLineTester_loadLibraryTests_0_FAILED( |
Ive determined that in JDK22 the exception is thrown and the application is termitnated, but for some reason the exception trace isnt printed. |
Also, I dont think this issue is windows specific. It failed on Linux for me. I think the issue is that in JDK22 instance main methods are turned on by default. The first time it tries to call main it fails, then it tries again 3 more times, it looks like that eats the pending exception. |
This test also failed with RI
|
I think the issue is the launcher code, it clears any exception after calling The JDK21 launcher code would check the exception and then print it. So this looks like a regression in openjdk code. |
Presumably the change is intentional? If so this becomes a test issue and the test needs to be updated. |
It may be a bug on their part. Either way, the test should be excluded on JDK22+ for the time being |
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.functional_x86-64_windows_Release_testList_1/1 |
Issue eclipse-openj9#18975 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Created #19171 to exclude the test. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.functional_x86-64_windows_Release_testList_1/8 Created #19409 |
Issue eclipse-openj9#18975 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Issue eclipse-openj9#18975 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
The exclude isn't working because we are using the v1.0.1-release branch and testenv which specifies the 0.44 openj9 branch. |
Failure link
From an internal build(
win10x86-svl-rt1-1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder
The text was updated successfully, but these errors were encountered: