Bug ID: JDK-8338712 Test runtime/cds/DeterministicDump.java fails File content different at byte #4, b0 = 96, b1 = 80

Type: Bug
Component: hotspot
Sub-Component: runtime
Affected Version: 24

Priority: P4
Status: Open
Resolution: Unresolved
OS: os_x
CPU: aarch64

Submitted: 2024-08-21
Updated: 2024-08-29

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 24
24Unresolved

The GHA test runner https://github.com/sendaoYan/jdk-ysd/actions/runs/10483060119/job/29035536958 report runtime/cds/DeterministicDump.java test failed, the test log snippet:
STDERR:
java.lang.RuntimeException: File content different at byte #4, b0 = 96, b1 = 80
	at DeterministicDump.compare(DeterministicDump.java:114)
	at DeterministicDump.doTest(DeterministicDump.java:73)
	at DeterministicDump.main(DeterministicDump.java:42)

I created a subtask JDK-8339288 to improve the test so we can see what's happening when the failures happens in GHA.
29-08-2024
There's a recent commit to the leyden/premain branch to address this test failure on Windows. Not sure if it would help in this incident. https://github.com/openjdk/leyden/commit/a5daf90b0e818194fd11e74569e72f6dc70c105c
23-08-2024
Okay. It seems GHA doesn't upload any artifacts apart from the jtr file so we don't have the actual logs to look at.
21-08-2024
I think this issue different to JDK-8335449. In JDK-8335449 this test fails with some jvm options, such as `-XX:+UseZGC -XX:-ZGenerational`. So the solution of JDK-8335449 is add 'vm.flagless'. This issue the test fails with default jvm options.
21-08-2024
Is this a re-occurrence of JDK-8335449
21-08-2024