JDITest failing on openjdk8_openj9 x86-64 Linux with JDWP option sysntax error #63
Labels
Comments
This was referenced Jan 11, 2018
Merged
|
The test has been temporarily excluded from the build : adoptium/aqa-tests#214 |
|
JDK8+OJ9 failure reproduced using latest JDK8+OJ9 release. JDK9+OJ9 failure reproduced using latest JDK11+OJ9 release Unable to reproduce JDK9+OJ9 failure using latest JDK9+OJ9 release, as system test code could not be built using it - see issue #248. |
|
Next step is to determine the last JDK8 release the JDITest passes with. |
|
Earliest AOJDK JDK8+OJ9 release available ... ... gives same failure. |
|
The first error is correct - I have also confirmed that with this PR content, JdiTest passes against this OJDK8+OJ9 release level ... ... and fails with the second identified error against this OJDK8+OJ9 release level ... The implication is that either something changed in the OJDK code or OJ9 code. My initial guess is it is the latter, so I'll move ahead from the passing release towards the failing release to narrow down the OJ9 code change window. |
|
JdiTest passes with ... |
|
JdiTest passes with ... |
|
JdiTest fails ... ... with ... |
|
So implication is that somewhere between openj9-0.11.0 and openj9-0.12.0 releases there was a regression which caused this problem and that regression remains. |
|
Test logs for passing/failing test - full_logs.tar.gz |
|
JdiTest passes with ... ... providing further evidence that the regression is in code introduced between openj9-0.11.0 release and openj9-0.12.0 release. |
|
Note - only BLI in this list (taken from the JdiTest.java source code) fails to pass ... |
|
Seems I may have been over-optimistic with my conclusions as the failure actually appears to be intermittent. |
|
TBC What was to be an Eclipse OJ9 issue - more investigation of OJDK levels + HS required - it's clearly not an OpenJ9 problem ... System test JdiTest is failing intermittently with the following ... I have isolated the failure down to just the BLI sub-test, all other sub-tests pass when this is not run (from 10 run sample against an OJDK 8 + OJ9 0.12.1 build and an OJDK 8 + HS build). Instructions on how to execute the test locally can be found here - https://github.com/AdoptOpenJDK/openjdk-systemtest/blob/master/README.md. You need to run Investigation of the failure rate shows intriguing results ... OpenJ9 ... Test logs ... HotSpot ... Test logs : console.out.gz console_2.out.gz Also, try some OSes other than Linux x86_64. |
|
@Mesbah-Alam Can you confirm when the BLI sub-test of JdiTest last consistently passed please ? Even the earliest OJDK8+OJ9 release build I can find is showing a 20% failure rate. |
|
Obtained the oldest Oracle JDK8 level (from JIM - dated March 2014) I could ... ... a 100x run showed a 46% failure rate - console_3.out.gz |
|
Request put in to gain access to the remainder of the Oracle JDK archive on JIM. |
|
Windows ... A 1000x run showed a 24.5% failure rate with JDK ... A 100x run showed a 34% failure rate with JDK ... |
|
|
Curiously, this run shows a failure on the first attempt with "Address already in use" despite there being no connections on either of the ports (changed intentionally from 30050->3050 and 30060->3060) from the beginning ... |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JDITest is failing on openjdk8_openj9 x86-64 Linux with JDWP option sysntax error as follows:
Build URL: https://ci.adoptopenjdk.net/view/System%20tests/job/openjdk8_j9_systemtest_x86-64_linux/26/
JDITest is also failing on openjdk9_openj9 Linux x86-x64 build, but with a different error:
Build URL: https://ci.adoptopenjdk.net/view/System%20tests/job/openjdk9_j9_systemtest_x86-64_linux/
The text was updated successfully, but these errors were encountered: