Several M&M tests were timing out in my stress testing runs thru
much of the JDK17 stress testing cycle:

vmTestbase/nsk/monitoring/stress/classload/load008/TestDescription.java
vmTestbase/nsk/monitoring/stress/classload/load009/TestDescription.java
vmTestbase/nsk/monitoring/stress/classload/unload002/TestDescription.java
vmTestbase/nsk/monitoring/stress/classload/unload008/TestDescription.java

Here's my notes:

+#
+# jdk-17+25_1_linux - observed in jdk-17+25 testing on 2021.06.03 on
+# Linux-X64 in slowdebug config:
+# jdk-17+25_2_linux - observed in jdk-17+25 testing on 2021.06.04 on
+# Linux-X64 in slowdebug config:
+# jdk-17+25_3_linux - observed in jdk-17+25 testing on 2021.06.05 on
+# Linux-X64 in slowdebug config:
+#ZZZ vmTestbase/nsk/monitoring/stress/classload/load008/TestDescription.java
+
+# jdk-17+25_1_linux - observed in jdk-17+25 testing on 2021.06.03 on
+# Linux-X64 in slowdebug config:
+# jdk-17+25_2_linux - observed in jdk-17+25 testing on 2021.06.04 on
+# Linux-X64 in slowdebug config:
+# jdk-17+25_3_linux - observed in jdk-17+25 testing on 2021.06.05 on
+# Linux-X64 in slowdebug config:
+#ZZZ vmTestbase/nsk/monitoring/stress/classload/load009/TestDescription.java
+
+# jdk-17+26_1_linux - observed in jdk-17+25 testing on 2021.06.11 on
+# Linux-X64 in slowdebug config:
+#ZZZ vmTestbase/nsk/monitoring/stress/classload/unload008/TestDescription.java

I'm not sure why my notes for
vmTestbase/nsk/monitoring/stress/classload/unload002/TestDescription.java
are missing, but that entry was also added in JDK17...

I checked my archive and found a single failure in an "adhoc" run:

$ ls -l thread_debug01_2/failures.linux-x86_64/TestDescription.jtr.slowdebug
-rw-r--r-- 1 dcubed green 68317 Jun 23 2021 thread_debug01_2/failures.linux-x86_64/TestDescription.jtr.slowdebug

so JDK17 time frame, but not in a regular promoted build stress test run.