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

[Vladimir Petko]

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.

[Vladimir Petko (vpa1977)]

Disabled failing tests for now: https://git.launchpad.net/ubuntu/+source/openjdk-17/diff/debian/tests/problems-armhf.txt?id=37ad99b06559da3ee8d7b56c7c970734d64fa318

[Vladimir Petko (vpa1977)]

Note: hotspot disabled on armhf -22

[Vladimir Petko (vpa1977)]

Fixed in july security release[1]

[1] https://launchpad.net/ubuntu/+source/openjdk-21/21.0.4+7-1ubuntu2~24.04