-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Unable to find mapped JDK in AdoptOpenJDK Docker images after mid-October #2031
Comments
Rerun Grinder [4314] with setting SDK_RESOURCE nightly instead of releases looks fine 4328 |
Also I can't figure out why https://ci.adoptopenjdk.net/view/Test_external/job/Test_openjdk8_j9_sanity.external_s390x_linux_tomee/ didn't run tomee_test_j9? I have pull lastest openjdk-tests and didn't see the testcase was disabled on s390? Curious |
Currently we mount the test jdk to The issue only happened when mount latest release jdk to nightly docker image
Mounted with nightly jdk to nightly docker image
Mounted with latest releases jdk to latest released docker image works fine:
Mounted with nightly jdk to latest released docker image works fine:
This is same for 11 and different platforms. Will see if it's same for hotspot. |
tomee was only disabled for jdk8 hs s390x (because of no JIT slowness): #1996 @bharathappali @dinogun - Do you have ideas of why we are seeing the behaviour described in #2031 (comment) |
@smlambert @sophia-guo Correct me if i'm wrong with the setup i have done below:
The SCC option is given EDIT : I would like to correct the sentence which i mentioned earlier above I wouldn't say that JVM is not coming up as if there is any error in VM startup OpenJ9 output's something like
Which is not seen in this case. Thanks and advance. |
@bharathappali yes, that's the issue we hit. And just update that hotspot doesn't have this issue. |
I'm seeing a strange behavior with this particular experiment of volume mounting the JDK
When i was running later a simple |
@sophia-guo Thanks for sharing this info, This makes it clear that the problem is with SCC (which is OpenJ9 specific) so hotspot is not having any problem. |
Move to build-docker repo AdoptOpenJDK/openjdk-docker#457 |
Starting in mid October (around Oct 14th), we see issues running java executable from a mapped drive using the 'nightly' images produced at the project and pushed to Docker hub. This was previously not an issue.
Suspect that something changed in the Docker images as test material and mapped JDK is unchanged when issue is present (so this may get shifted to openjdk-docker repo after additional investigation).
Running Tomee tests using the JDK from within the AdoptOpenJDK Docker image,
https://ci.adoptopenjdk.net/job/Grinder/4315/console you can see that the tests execute and run:
Running same Tomee tests with mapped drive to nightly JDK build, Grinder 4314, unable to determine mapped JDK (JAVA VERSION OUTPUT is empty).
The text was updated successfully, but these errors were encountered: