The following test failed in the JDK17 CI:

com/sun/jdi/JdbOptions.java

Here's a snippet from the log file:

The application exited
]
 exitValue = -1

java.lang.RuntimeException: 'prop[boo] = >foo<' missing from stdout/stderr

at jdk.test.lib.process.OutputAnalyzer.shouldContain(OutputAnalyzer.java:206)
at JdbOptions$TestResult.expectedProp(JdbOptions.java:140)
at JdbOptions.main(JdbOptions.java:93)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:831)

JavaTest Message: Test threw exception: java.lang.RuntimeException: 'prop[boo] = >foo<' missing from stdout/stderr

JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.RuntimeException: 'prop[boo] = >foo<' missing from stdout/stderr
----------rerun:(39/6323)*----------

This failure mode is very similar to:

JDK-8259266 com/sun/jdi/JdbOptions.java failed with "RuntimeException: 'prop[boo] = >foo 2<' missing from stdout/stderr"

but the fix for that bug was integrated on 2021.01.15.