[Bug 2073335] [NEW] openjdk-17, -21, 23 armhf: multiple jtreg test failures due to the time_t transition

[Vladimir Petko]

Public bug reported:

The issue is caused by 64 bit time_t transition.

Multiple jtreg tests fail in Ubuntu noble, armhf because they assert the
file modification time:

jdk/nio/zipfs/CopyMoveTests.java
jdk/nio/zipfs/TestPosix.java
java/nio/file/attribute/BasicFileAttributeView/Basic.java
java/nio/file/attribute/BasicFileAttributeView/CreationTime.java
java/nio/file/Files/SetLastModifiedTime.java
java/nio/file/Files/SymlinkTime.java
tools/javac/modules/MOptionTest.java

runtime/cds/appcds/dynamicArchive/DynamicSharedSymbols.java
runtime/cds/appcds/jcmd/JCmdTestDynamicDump.java
runtime/cds/appcds/jcmd/JCmdTestFileSafety.java
runtime/cds/appcds/jcmd/JCmdTestStaticDump.java
runtime/cds/appcds/RelativePath.java
runtime/jcmd/JcmdCmdLine.java
serviceability/attach/AttachNegativePidTest.java
serviceability/attach/RemovingUnixDomainSocketTest.java
serviceability/HeapDump/DuplicateArrayClassesTest.java
serviceability/HeapDump/FieldsInInstanceTest.java

The file modification time is set in sun.nio.fs.UnixFileAttributeViews.setTimes() method, that calls
Java_sun_nio_fs_UnixNativeDispatcher_futimens0 in 'src/java.base/unix/native/libnio/fs/UnixNativeDispatcher.c'.

The function pointer my_futimens_func has the version of the function
that assumes 32 bit time_t, causing the failure to set last modification
time.

** Affects: openjdk-17 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: openjdk-21 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: openjdk-23 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openjdk-17 in Ubuntu.
https://bugs.launchpad.net/bugs/2073335

Title:
  openjdk-17,-21,23 armhf:  multiple jtreg test failures due to the
  time_t transition

Status in openjdk-17 package in Ubuntu:
  New
Status in openjdk-21 package in Ubuntu:
  New
Status in openjdk-23 package in Ubuntu:
  New

Bug description:
  The issue is caused by 64 bit time_t transition.

  Multiple jtreg tests fail in Ubuntu noble, armhf because they assert
  the file modification time:

  jdk/nio/zipfs/CopyMoveTests.java
  jdk/nio/zipfs/TestPosix.java
  java/nio/file/attribute/BasicFileAttributeView/Basic.java
  java/nio/file/attribute/BasicFileAttributeView/CreationTime.java
  java/nio/file/Files/SetLastModifiedTime.java
  java/nio/file/Files/SymlinkTime.java
  tools/javac/modules/MOptionTest.java

  runtime/cds/appcds/dynamicArchive/DynamicSharedSymbols.java
  runtime/cds/appcds/jcmd/JCmdTestDynamicDump.java
  runtime/cds/appcds/jcmd/JCmdTestFileSafety.java
  runtime/cds/appcds/jcmd/JCmdTestStaticDump.java
  runtime/cds/appcds/RelativePath.java
  runtime/jcmd/JcmdCmdLine.java
  serviceability/attach/AttachNegativePidTest.java
  serviceability/attach/RemovingUnixDomainSocketTest.java
  serviceability/HeapDump/DuplicateArrayClassesTest.java
  serviceability/HeapDump/FieldsInInstanceTest.java

  The file modification time is set in sun.nio.fs.UnixFileAttributeViews.setTimes() method, that calls
  Java_sun_nio_fs_UnixNativeDispatcher_futimens0 in 'src/java.base/unix/native/libnio/fs/UnixNativeDispatcher.c'.

  The function pointer my_futimens_func has the version of the function
  that assumes 32 bit time_t, causing the failure to set last
  modification time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2073335/+subscriptions