-
Bug
-
Resolution: Fixed
-
P3
-
15
-
b22
The most common causes for this kind of issues are binary formats that contains raw, unsorted dumps of hash maps, and timestamps. Fixing the output so it remains stable upon repeated runs on the same environment makes it possible to verify the consistency of the build.
In some rare cases, there have been other bugs hiding in non-determinism. It is also good to be sure that the cause for non-determinism in classes.jsa is not such a bug.
I'm currently making a change in the build system, where I'd like to be more sure that I do not affect the content of classes.jsa. So if this is possible to fix relatively soon, I'd be very happy.
----
Review thread: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2020-April/039135.html
----
For debugging determinism issues with classes.jsa, see https://wiki.openjdk.java.net/display/HotSpot/Debugging+CDS+DeterministicDump.java+test+failures
- is blocked by
-
JDK-8243936 NonWriteable system properties are actually writeable
- Resolved
-
JDK-8241271 Make hotspot build reproducible
- Resolved
- relates to
-
JDK-8245335 [TESTBUG] DeterministicDump.java fails with release JVM
- Resolved
-
JDK-8335449 runtime/cds/DeterministicDump.java fails with File content different at byte ...
- Resolved
-
JDK-8244489 Zero and minimal VM build failure after JDK-8241071 (MetaspaceShared::symbol_space_alloc is undefined)
- Resolved
-
JDK-8244536 cds/DeterministicDump.java failed: File content different
- Resolved
-
JDK-8275867 Make ImmutableCollections deterministic if running with TraceBytecodes/StopInterpreterAt
- Closed