The following test timed out in the JDK17 CI:

sun/util/resources/cldr/TimeZoneNamesTest.java

Here's a snippet from the log file:

#section:testng
----------messages:(7/340)----------
command: testng -Djava.locale.providers=CLDR TimeZoneNamesTest
reason: User specified action: run testng/othervm -Djava.locale.providers=CLDR TimeZoneNamesTest
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules jdk.localedata
Timeout information:
--- Timeout information end.
elapsed time (seconds): 516.23
----------configuration:(3/42)----------
Boot Layer
  add modules: jdk.localedata

----------System.out:(3110/72214)----------
[TestNG] Running:
  sun/util/resources/cldr/TimeZoneNamesTest.java

Locale:
    tz: UTC
    tz: Etc/UTC

<snip>

    tz: America/Argentina/Buenos_Aires
    tz: Europe/Nicosia
    tz: US/Pacific
Locale: ff_SN_#Latn
----------System.err:(0/0)----------
----------rerun:(40/5947)*----------

<snip>

result: Error. Program `/opt/mach5/mesos/work_dir/jib-master/install/jdk-17+9-600/linux-x64-debug.jdk/jdk-17/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 516204ms).

The JVM args for this test task are: -Xcheck:jni

This makes me wonder if the JNI checking combined
with fastdebug has really slowed down this test.