Open Akira1Saitoh opened 4 years ago
The 0.21.0 m1 build takes 785 seconds on cent7-aarch64-1 to run this test. Timeout value is 960 seconds.
We should find out how long this test takes to run on x86 for relative comparison. If there is a wide difference then there might be something pathologically wrong with AArch64 (e.g., methods are being interpreted) rather than just device slowness.
@0xdaryl It seems java/net tests are not executed in sanity.openjdk now, and I don't have numbers. https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_x86-64_linux/256/testReport/ https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_ppc64le_linux/260/testReport/
My local AArch64 build with recompilation runs this test in 420 seconds on cent7-aarch64-1, 47% shorter than 785 seconds without recompilation.
I believe this issue can be closed. The test has been enabled since June last year.
Failure link
https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_aarch64_linux/101/testReport/junit/java_net_httpclient_websocket_ReaderDriver/java/ReaderDriver/
Optional info
Failure output (captured from console output)
This test is known to intermittently timeout on aarch64. We will add this test to the exclude list and revisit later.