-
Notifications
You must be signed in to change notification settings - Fork 723
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_nonPortableRestoreJDK11Up testObjectWaitTimedV2 actual elapsed time does not match expected #16907
Comments
@tajila fyi |
@JasonFengJ9 Please take a look |
There was a mismatching openj9/test/functional/cmdLineTests/criu/src/org/openj9/criu/JDK11UpTimeoutAdjustmentTest.java Lines 232 to 233 in 5938c2f
The actual elapsed time was 9888ms compared with the target 10000ms , will check System.nanoTime() and Object.wait() time compensation across C/R.
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_s390x_linux_OMR_testList_0/424
|
This failure occurred before checkpoint, |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_s390x_linux_Nightly_testList_0/519/
|
@JasonFengJ9 does this still fail? |
Any recent failures would have been added to the appropriate issues (except during my vacation times), so no. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_sanity.functional_x86-64_linux_Nightly_testList_1/129
cmdLineTester_criu_nonPortableRestoreJDK11Up_0
The text was updated successfully, but these errors were encountered: