cmdLineTester_criu_jitserverPostRestore zLinux assertion JITServerPersistentCHTable.cpp:172 #17474
Assignees
Labels
comp:jit
comp:jitserver
Artifacts related to JIT-as-a-Service project
criu
Used to track CRIU snapshot related work
test failure
Milestone
Comments
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_OMR_testList_1/345 |
pshipton
changed the title
pshipton
changed the title
|
@dsouzai ^^ |
|
Because of this message: It looks like the crash is on the JITserver instance, and not on the restored JVM (a crash in the restored JVM wouldn't bring down the jitserver instance). @mpirvu do you have any ideas as to what could be going on here? |
|
I have seen that message when the client was not generating a new clientUID after restore. From the diagnostic data I cannot tell the UID of the client before the checkpoint and after the restore to determine that they are different. |
Why would that cause the JITServer instance to go down? Shouldn't it just reject the client? |
|
The server thinks it's the same client and that it encountered a bug. Rather than reject the client and hide the bug, we prefer to fatal assert. |
|
Because this message is coming from the jitserver, if it did fatal assert because the client failed to generate a new UID, we should see that assert in the output. However, maybe what I'll do is update the tests to have better separation of the the various things that get |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_Nightly_testList_0/509 |
tajila
modified the milestones:
Release 0.41 (Java 8, 11, 17) Oct refresh,
Release 0.43 (Java 8, 11, 17, 21) Jan refresh
|
JDK21 s390x_linux( |
tajila
modified the milestones:
Release 0.43 (Java 8, 11, 17, 21) Jan refresh,
Release 0.44 (Java 8, 11, 17, 21) Apr refresh
tajila
modified the milestones:
Release 0.43 (Java 8, 11, 17, 21) Jan refresh,
Release 0.44 (Java 8, 11, 17, 21) Apr refresh
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.functional_s390x_linux_Release_testList_1/4 |
|
JDK17 s390x_linux( |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.functional_aarch64_linux_Release_testList_0/11 |
|
@dsouzai Is this something we're looking at for the 0.48 release? |
|
No; I spent some time a few months ago looking at this but couldn't make much progress. It's fairly intermittent and seems to only happen with JITServer + CRIU. |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_s390x_linux_Release_testList_0/122 |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk23_j9_sanity.functional_ppc64le_linux_Nightly_testList_0/41/ |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_ppc64le_linux_OMR_testList_1/85\ |
|
@dsouzai, should this move out to the 0.51 release? |
Yes, in my opinion. |
|
Yeah I agree, it's an issue that only seems to happen on zLinux with JITServer + CRIU. I've tried looking into it a while back but it's so intermittent that I haven't been able to make much progress. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failure link
From an internal build(
rhel7s390x-4-1):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - all passed
FYI @tajila
The text was updated successfully, but these errors were encountered: