-
Bug
-
Resolution: Fixed
-
P4
-
19
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8280145 | 17.0.3 | Andrew Leonard | P4 | Resolved | Fixed | b01 |
$ CONF=linux-x86-server-fastdebug make run-test TEST=tools/jar/ReproducibleJar.java
Checking jar entries local date time for --date 2099-12-31T23:59:59+00:00, is 2099-12-31T23:59:59
test ReproducibleJar.testValidSourceDate("2099-12-31T23:59:59+00:00"): failure
java.lang.AssertionError: checkFileTime failed, extracted to 1963-11-25T16:31:42Z, expected to be close to 2099-12-31T22:59:59Z
at ReproducibleJar.checkFileTime(ReproducibleJar.java:243)
at ReproducibleJar.testValidSourceDate(ReproducibleJar.java:152)
This is due to JDK-8279444, which cannot be solved yet. This test might need to be disabled on 32-bit platforms meanwhile.
- backported by
-
JDK-8280145 Disable tools/jar/ReproducibleJar.java on 32-bit platforms
-
- Resolved
-
- relates to
-
JDK-8279444 File.setLastModifiedTime(long) suffers from Year 2038 problem on 32-bit platforms
-
- Open
-
-
JDK-8276766 Enable jar and jmod to produce deterministic timestamped content
-
- Resolved
-
- links to
-
Commit openjdk/jdk17u-dev/761e2989
-
Commit openjdk/jdk/a741b927
-
Review openjdk/jdk17u-dev/82
-
Review openjdk/jdk/6957
(2 links to)