-
Notifications
You must be signed in to change notification settings - Fork 721
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_jitserverAcrossCheckpoint Success condition was not found: [Output match: Connected to a server] #17324
Comments
Yeah I think this is the same issue; looks like the shutdown sequence interrupted the compilation thread before it had a chance to connect to the jitserver instance. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_sanity.functional_x86-64_linux_OMR_testList_1/12
|
Not in this case; this test is sort of a multi-test test, namely:
This set of tests works in the following way:
Because these tests involve both jitserver and criu, it's kind of tricky to test the state of things pre-checkpoint and post-restore. All that said, I'm not really sure what's going on here. If the jitserver instance didn't exist, I would've expected to see a message in the post-restore vlog that showed a failed connection. However, I don't see any such message, which implies that the JVM didn't even bother trying to connect. I'm not sure something like this wouldn't have shown up in the PR tests unless there's something specific to x86. EDIT: not sure that's a valid argument because literally every other build (including x86) passed. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_OMR_testList_0/336
|
I believe this is another instance of #17367 (since the test before the |
Seeing a failure in my personal build that look related to this. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_OMR_testList_0/318/
cmdLineTester_criu_jitserverAcrossCheckpoint_0
The text was updated successfully, but these errors were encountered: