Error. compiler crashed (exit code 4) - cannot access unnamed package #20786

[JasonFengJ9]

Failure link

From internal Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_2 (win22x86-svl-rt7-1)

openjdk version "23.0.1-beta" 2024-10-15
IBM Semeru Runtime Open Edition 23.0.1+11-202501210331 (build 23.0.1-beta+11-202501210331)
Eclipse OpenJ9 VM 23.0.1+11-202501210331 (build master-63f23a3112, JRE 23 Windows Server 2022 amd64-64-Bit Compressed References 20250121_91 (JIT enabled, AOT enabled)
OpenJ9   - 63f23a3112
OMR      - 6bfb20f78
JCL      - d98479bbe based on jdk-23.0.1+11)

Rerun in Grinder - Change TARGET to run only the failed test targets

Optional info

Failure output (captured from console output)

[2025-01-21T10:11:47.319Z] variation: -Xdump:system:none -Xdump:heap:none -Xdump:system:events=gpf+abort+traceassert+corruptcache -XX:-JITServerTechPreviewMessage Mode650
[2025-01-21T10:11:47.319Z] JVM_OPTIONS:  -Xdump:system:none -Xdump:heap:none -Xdump:system:events=gpf+abort+traceassert+corruptcache -XX:-JITServerTechPreviewMessage -XX:-UseCompressedOops -Xverbosegclog 

[2025-01-21T10:12:57.570Z] TEST: java/lang/IntegralPrimitiveToString.java

[2025-01-21T10:12:57.571Z] C:\Users\jenkins\workspace\Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_2\aqa-tests\openjdk\openjdk-jdk\test\jdk\java\lang\IntegralPrimitiveToString.java:24: error: cannot access unnamed package
[2025-01-21T10:12:57.571Z] import org.testng.annotations.DataProvider;
[2025-01-21T10:12:57.571Z] ^
[2025-01-21T10:12:57.571Z]   /com/google/inject/internal/util/StackTraceElements$InMemoryStackTraceElement.class
[2025-01-21T10:12:57.571Z] 1 error
[2025-01-21T10:12:57.571Z] printing javac parameters to: C:\temp\javac.20250121_021254.args
[2025-01-21T10:12:57.571Z] 
[2025-01-21T10:12:57.571Z] TEST RESULT: Error. compiler crashed (exit code 4)

[2025-01-21T11:55:31.319Z] C:\Users\jenkins\workspace\Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_2\aqa-tests\openjdk\openjdk-jdk\test\jdk\sun\reflect\ReflectionFactory\ReflectionFactoryTest.java:24: error: cannot access unnamed package
[2025-01-21T11:55:31.319Z] import java.io.ByteArrayInputStream;
[2025-01-21T11:55:31.319Z] ^
[2025-01-21T11:55:31.319Z]   /com/beust/jcommander/ParameterDescription$SubParameterIndex.class
[2025-01-21T11:55:31.319Z] 1 error
[2025-01-21T11:55:31.319Z] printing javac parameters to: C:\temp\javac.20250121_035530.args
[2025-01-21T11:55:31.319Z] 
[2025-01-21T11:55:31.319Z] TEST RESULT: Error. compiler crashed (exit code 4)
[2025-01-21T11:55:31.319Z] --------------------------------------------------
[2025-01-21T11:55:59.869Z] Test results: passed: 633; failed: 5; error: 293
[2025-01-21T11:56:34.377Z] Report written to C:\Users\jenkins\workspace\Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_2\aqa-tests\TKG\output_17374542963639\jdk_lang_1\report\html\report.html
[2025-01-21T11:56:34.377Z] Results written to C:\Users\jenkins\workspace\Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_2\aqa-tests\TKG\output_17374542963639\jdk_lang_1\work
[2025-01-21T11:56:34.377Z] Error: Some tests failed or other problems occurred.
[2025-01-21T11:56:34.377Z] -----------------------------------
[2025-01-21T11:56:34.377Z] jdk_lang_1_FAILED

openjdk23_j9_sanity.openjdk_x86-64_linux
openjdk21_j9_extended.openjdk_x86-64_linux
openjdk21_j9_extended.openjdk_x86-64_linux

There was a similar issue

• Error. compiler crashed (exit code 4) - cannot access unnamed package #20786

FYI @hzongaro

[hzongaro]

@a7ehuo, may I ask you to take a look at this problem?

[a7ehuo]

I'm trying to reproduce this failure locally with JDK21 on x86-64 linux machine. With jdk11_tier1_buffer_1, 120 runs all passed. I'm gonna try jdk_other_1 as well since jdk_other_1 seems to have more failures.

[llxia]

We also see this issue on RHEL10. In our case, it was jdk_vector_1 with a high failure rate. For details, see link

[hzongaro]

I was also able to reproduce that compiler crash in an internal grinder run running jdk_security1_1 and jdk_security2_1.

By the way, the previous problem with a similar symptom — #20786 — was caused by unbalanced Start internal control flow and End internal control flow labels. On the off chance that this is caused by the same problem, you might try picking up this draft OMR pull request eclipse-omr/omr#7597 to see whether it hits any assertions running sanity.openjdk. I was successful running testing with it on x86.