-
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
DaaLoadTest_daa1 tests - **FAILED** Process DLT has hung #13477
Comments
Also occurred at JDK17 M1 internal build
Since this occurred at JDK17, move it to |
Observed in JDK17
Also observed at JDK11
|
Observed at JDK11
|
The message "Completed 100.0%. Number of tests started=10" in the console output suggests this might be a test issue. As per It appears that @Mesbah-Alam @llxia any insights? I think this is not a [1] https://github.com/adoptium/STF/blob/master/stf.load/docs/README.md |
@Mesbah-Alam could you take a look into this? Thanks |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_ppc64_aix_Release_testList_2/8 - aix71-p8-6
|
As described in issue #13726, in The Java method that's being compiled - Caching the fact that a |
Fixed in pull request #13885 |
JDK19 milestone build 1(
|
Failed 11/50 |
It is not clear how many unique problems we're seeing running this test. The last real investigation concluded there was a pathologically large JIT method causing the timeouts, however other failures reported in the past year seem to suggest there are other issues (though they could all be connected in some way). This needs to be sorted out but it won't happen for 0.38. I'll at least commit to have someone look into the long JIT compilation in the coming months, but won't commit to a milestone just yet. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_special.system_x86-64_windows_Personal_testList_2/6/ - win2019x64-openj9-5
Running slowly or looping.
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_special.system_x86-64_windows_Personal_testList_3/7 - win2019-x64-3
javacore 2
javacore 4
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_x86-64_windows_Release_testList_2/49 - win2019x64-openj9-1
Seems to be running slowly or looping.
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_special.system_x86-64_windows_Personal_testList_3/8 - win2019x64-openj9-4
Seems to be running slowly or looping.
|
Seems to me the win2019 machines are slower than the older win2012 machines. I wonder if the test just times out too quickly for these machines. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_special.system_x86-64_windows_Personal_testList_3/9 - win2019x64-openj9-4/9/system_test_output.tar.gz
|
I'm going to start ignoring failures that match this pattern, hang on win2019 machines. |
@AdamBrousseau fyi this failure which appears to be related to win 2019 machines being too slow. |
JDK11 aarch64_mac 0.38(
No diagnostics. |
JDK20 x86-64_windows(
|
@JasonFengJ9 pls ignore DaaLoadTest mode 24 hangs on Windows. |
JDK21 aarch64_mac milestone 0(
|
Moving this to the backlog for now, but I will try to spend some time sorting out whether there are distinct JIT problems here that can be tracked and prioritized as separate issues. |
JDK11 aarch64_mac(
Another similar one DaaLoadTest_daa1_special_5m_24_FAILED at same machine. |
JDK22 x86-64_windows(
|
openjdk21_j9_special.system_x86-64_windows(
|
Failure link
From an internal build
Test_openjdk11_j9_special.system_ppc64le_linux_testList_2/111/
(ubu18le-rt1-4
):Re-run the Grinder
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: