Open sophia-guo opened 3 years ago
Exploration done till now (Adding here for quick reference): https://github.com/AdoptOpenJDK/openjdk-tests/issues/2031#issuecomment-719985342 https://github.com/AdoptOpenJDK/openjdk-tests/issues/2031#issuecomment-721591801
@sophia-guo I have raised an issue in OpenJ9 https://github.com/eclipse/openj9/issues/11110
I have pointed your issue in AdoptOpenJDK/openjdk-tests#2031 as it has more details than this issue in openjdk-docker repo.
From the conversation at OpenJ9 issue https://github.com/eclipse/openj9/issues/11110#issuecomment-723190325 , It looks like the current SCC mechanism is not handling a mismatch wrt SCC generated by different builds as expected. A quick possible workaround would be to repopulate the cache by removing readOnly
when we mount the jdk and run the tests.
so while running docker we add a env var OPENJ9_JAVA_OPTIONS
and set it to -Xshareclasses:name=openj9_system_scc,cacheDir=/opt/java/.scc,nonfatal
Eg :
docker run --rm -e OPENJ9_JAVA_OPTIONS=-Xshareclasses:name=openj9_system_scc,cacheDir=/opt/java/.scc,nonfatal -v /Users/sophiag/Downloads/dockermount/jdk8u272-b10_release:/opt/java/openjdk -it adoptopenjdk/openjdk8-openj9:nightly java -version
So that the cache is re-created, JVM starts up without any error (related to SCC) and tests can be performed.
@dinogun @smlambert @sophia-guo Can i have your views on this workaround ?
https://github.com/eclipse/openj9/pull/11213 fixes the issue of JVM crashing on nightly build SCC.
I hope the next release of OpenJ9 will have the changes to fix this problem.
EDIT:
FYI - https://github.com/eclipse/openj9/pull/11213#issuecomment-729234590
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).
Details in https://github.com/AdoptOpenJDK/openjdk-tests/issues/2031
https://github.com/AdoptOpenJDK/openjdk-tests/issues/2031#issuecomment-719949546