-
Notifications
You must be signed in to change notification settings - Fork 738
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
AArch64 macOS: Failure in JDK 11 ASSERTION FAILED ParallelScavengeTask.cpp:120 ((false && ((endTime - startTime) >= _syncCriticalSectionDuration))) #14636
Comments
May be related to #13368 |
Ignore the previous comment, there is additional output
|
I ran Grinder jobs below, and they were successful. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.system_aarch64_mac_Nightly_testList_0/3 - mac11-aarch64-8
|
20x Grinder jobs for LambdaLoadTest_J9_5m_0 did not fail: internal job/Grinder/21639/ , job/Grinder/21641/ , job/Grinder/21643/ , job/Grinder/21644/ |
Possible causes:
|
Grinder jobs for jdk_lang_1 did not fail: internal job/Grinder/21661/, job/Grinder/21665/, job/Grinder/21666/ |
Reproduced in job/Test_openjdk18_j9_special.system_aarch64_mac_Personal_testList_4/1/consoleText in running DaaLoadTest_all_special_5m_9.
|
I ran a 20x Grinder job for DaaLoadTest_all_special_5m_9 in job/Grinder/22364/, and got no failures. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk18_j9_special.system_aarch64_mac_Personal_testList_0/2
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_aarch64_mac_Release_testList_4/2 |
Sorry, I missed there is assertion in GC code This is snap traces:
I believe last two lines are in incorrect order due both have the same time stamp There are two threads performed GC operation:
As was stated correctly in the comment #14636 (comment) |
DDR implementation for AArch64 macOS is in progress in eclipse-omr/omr#6471 and #14921. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_aarch64_mac_Personal_testList_4/8
DaaLoadTest_all_special_5m_9
More in |
@pshipton Do you know, is DDR available for this build? |
No, there is no DDR support for amac yet. Perhaps tomorrow. |
amac DDR is now enabled in future builds. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_aarch64_mac_Release_testList_4/3 - mac11-aarch64-6
@dmitripivkine fyi - DDR is enabled now. |
This assertion does check that waiting time in the |
The execution time for thread performed single threaded operation was very short in this case. I have not looked in c-stack/registers for values in ticks but Snap traces shows 0us difference, so it was under 1us. And somehow EndTime (taken at the end) is smaller by 25 ticks as StartTime(taken at the beginning). Can actually wall clock adjustment (backwards) be visible by one thread and missed by another? |
In order to get time GC code uses |
I wonder why the failure happens only on AArch64 macOS if it is caused by lacking the monotonicity of the clock. |
I opened eclipse-omr/omr#6568 for monotonic
|
eclipse-omr/omr#6568 was superseded by eclipse-omr/omr#6573. |
OMR PR 6573 was merged. Let's see if the assertion failure is reproduced or not with the change. |
It is a week since OMR PR 6573 was merged, and I don't think we have seen a new failure. |
I opened eclipse-openj9/openj9-omr#150 for v0.33.0. It is in the draft state. |
I've merged it. |
Failure link
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.openjdk_aarch64_mac_Nightly/2/ - mac11-aarch64-4
Optional info
Failure output (captured from console output)
No output available: Only
Unexpected exit from test [exit code: 255]
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.openjdk_aarch64_mac_Nightly/2/testReport/junit/java_lang_invoke_VarHandles_VarHandleTestByteArrayAsInt/java/VarHandleTestByteArrayAsInt/
The text was updated successfully, but these errors were encountered: