-
Notifications
You must be signed in to change notification settings - Fork 735
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
cmdLineTester_criu_nonPortableRestore_Xtrace_tracepoint - Blocking operation is not allowed in CRIU single thread mode #18399
Comments
@TobiAjila fyi |
@TobiAjila I see failures in cmdLineTester_criu_nonPortableRestore tests all the time for the past few weeks, are we working to fix that? Some of them are #18384 |
Yes @JasonFengJ9 Is looking into it |
@singh264 Can you please take a look at this. You can generate a system core when the |
@tajila I generated a system core file when |
The blocking operation seems to occur during the During the test failure, the code path taken from
|
@tajila How could a blocking operation be supported for CRIU single thread mode during the |
We dont support blockign operations in single thread mode. The way to address this is to determine which thread owns the contended resource, then make sure that thread is not halted while holding the resource with |
Although I put this into the 0.43 milestone, we also get "Blocking operation is not allowed in CRIU single thread mode." failures in jdk21 builds. https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_aarch64_linux_Nightly_testList_1/98/
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_s390x_linux_Nightly_testList_1/98/
|
Add NotCheckpointSafe annotations to PhantomCleanable to avoid blocking operations during restore in CRIU single thread mode, and fix the failures in the cmdLineTester_criu_nonPortableRestore tests that occur due to blocking operations during restore in CRIU single thread mode. Issue: eclipse-openj9/openj9#18399 Signed-off-by: Amarpreet Singh <[email protected]>
Add NotCheckpointSafe annotations to PhantomCleanable to avoid blocking operations during restore in CRIU single thread mode, and fix the failures in the cmdLineTester_criu_nonPortableRestore tests that occur due to blocking operations during restore in CRIU single thread mode. Issue: eclipse-openj9/openj9#18399 Signed-off-by: Amarpreet Singh <[email protected]>
Resolved via ibmruntimes/openj9-openjdk-jdk21#69 |
Also encountered this "Blocking operation is not allowed in CRIU single thread mode" in a pull request test of JDK 17 on aarch64: https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_aarch64_linux_Personal/369/ |
@singh264 Please take a look |
Add NotCheckpointSafe annotations to PhantomCleanable to avoid blocking operations during restore in CRIU single thread mode, and fix the failures in the cmdLineTester_criu_nonPortableRestore tests and the cmdLineTester_criu_nonPortableRestore_Xtrace_outputFile tests that occur due to blocking operations during restore in CRIU single thread mode. Issues: eclipse-openj9/openj9#18399, eclipse-openj9/openj9#18514 Signed-off-by: Amarpreet Singh <[email protected]>
This issue can be closed and it was fixed by:
The changes for JDK21 and JDK17 are in |
Closing as per #18399 (comment). |
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_aarch64_linux_OMR/41/
cmdLineTester_criu_nonPortableRestore_Xtrace_tracepoint_4
-Xgcpolicy:optavgpause
The text was updated successfully, but these errors were encountered: