-
Notifications
You must be signed in to change notification settings - Fork 736
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
(0.48) -agentpath: libraries require no path/name decoration & Refactor a few CRIU APIs to take J9JavaVM* instead of J9VMThread* #20287
(0.48) -agentpath: libraries require no path/name decoration & Refactor a few CRIU APIs to take J9JavaVM* instead of J9VMThread* #20287
Conversation
The currentThread passed into isCRaCorCRIUSupportEnabled(J9VMThread*), isCheckpointAllowed(J9VMThread*) and isDebugOnRestoreEnabled(J9VMThread*) are just for redirection of currentThread->javaVM, changed the APIs to take J9JavaVM* directly. Signed-off-by: Jason Feng <[email protected]>
The agent library specified via -agentpath: has an absolute path/name, it should not be decorated again during the agent library loading; For -agentpath: option in the restore option file, compare the actual platform-dependent library name. Signed-off-by: Jason Feng <[email protected]>
Is the failure in https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.system_aarch64_mac_Release/86/ related to the #20202? If we think so, that should be fixed before propagating to the 0.48 release branch. |
This is to be fixed by this PR in 0.48. |
I think the problem is in https://github.com/adoptium/openj9-systemtest/blob/master/openj9.test.sharedClasses.jvmti/src/test.sharedClasses.jvmti/net/openj9/stf/SharedClassesAPI.java#L216 so I don't see how this could fix that. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.system_aarch64_mac_Release/86/
The wrong library name was due to additional decoration introduced by #19754 which was merged into 0.48 this morning, the build was launched afterwards but w/o this PR. |
I think adoptium/openj9-systemtest#158 is needed to fix that failure. |
The problem seen in https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.system_aarch64_mac_Release/86/ was fixed in the head stream via #20202 |
-agentpath:
libraries require no path/name decorationThe agent library specified via
-agentpath:
has an absolute path/name, it should not be decorated again during the agent library loading;For
-agentpath:
option in the restore option file, compare the actual platform-dependent library name.Cherry-pick
Refactor a few CRIU APIs to take
J9JavaVM*
instead ofJ9VMThread*
The currentThread passed into
isCRaCorCRIUSupportEnabled(J9VMThread*)
,isCheckpointAllowed(J9VMThread*)
andisDebugOnRestoreEnabled(J9VMThread*)
are just for redirection ofcurrentThread->javaVM
, changed the APIs to takeJ9JavaVM*
directly.Cherry-pick
Note: these two PRs were in last night's builds, and no failure seems related to those changes.
In addition, there were merging conflicts, verified in a personal build JDK17_x86-64_linux.
Signed-off-by: Jason Feng [email protected]