-
Notifications
You must be signed in to change notification settings - Fork 720
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_0_FAILED testTimeCompensation() after CRIU restore elapsedMillisTime should NOT be greater than maxElapsedMillisTime or delayed elapsedMillisTime should NOT be less than minElapsedMillisTime #18513
Comments
Encountered this failure in a pull request test run on aarch64 Linux. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_aarch64_linux_Nightly_testList_0/105/
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.functional_aarch64_linux_Nightly_testList_0/106/ |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_aarch64_linux_Nightly_testList_0/578 |
This wasn't the initial failure for this issue |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_x86-64_linux_OMR_testList_1/493
|
There was no sub-test failure since |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_aarch64_linux_Nightly_testList_0/637 |
JDK17 aarch64_linux(
50x grinder - passed |
Failure link
From https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_Nightly/603/tapResults/
Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
This is a test issue, the
maxElapsedMillisTime
needs further adjustment for zLinux machines.The text was updated successfully, but these errors were encountered: