The following test failed in the JDK19 CI:

applications/cassandrastress/CassandraStressTest.java

Here's a snippet from the log file:

The stress VM is running but modules are not ready yet.
Will sleep 30000 ms before next check.
The stress VM is running but modules are not ready yet.
Will sleep 30000 ms before next check.
Got an exception, so I'll kill the stress process process
[Fri Dec 17 15:55:44 UTC 2021] Unexpected errors during GlueModule initialization: Stress process finished unexpectedly with exit code 134
java.lang.RuntimeException: Stress process finished unexpectedly with exit code 134
at applications.kitchensink.process.glue.Main.waitUntilStressProcessReady(Main.java:422)
at applications.kitchensink.process.glue.Main.execute(Main.java:330)
at applications.kitchensink.process.glue.Main.main(Main.java:217)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:577)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:833)

JavaTest Message: Test threw exception: java.lang.RuntimeException: Stress process finished unexpectedly with exit code 134
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Stress process finished unexpectedly with exit code 134
----------rerun:(38/8151)*----------

This failure was spotted in jdk-19+3-72-tier3 and the fix for this bug:

JDK-8278931 CassandraStressTest.java fails to check that server started

was integrated in jdk-19+3-69.