----------messages:(6/301)----------
command: main -Xms50M -Xmx200M nsk.stress.except.except011
reason: User specified action: run main/othervm -Xms50M -Xmx200M nsk.stress.except.except011
started: Sun Dec 25 22:18:35 UTC 2022
Mode: othervm [/othervm specified]
finished: Sun Dec 25 22:18:38 UTC 2022
elapsed time (seconds): 3.078
----------configuration:(0/0)----------
----------System.out:(20/978)----------
# While printing this message, JVM seems to initiate the output
# stream, so that it will not need more memory to print later,
# when the heap would fail to provide more memory.
#
# Note, that the test maintains especial static log[] field in
# order to avoid printing when the heap seems exhausted.
# Nevertheless, printing could arise OutOfMemoryError even
# after all the memory allocated by the test is released.
#
# That problem is caused by the known JDK/HotSpot bugs:
# 4239841 (P1/S5) 1.1: poor garbage collector performance
# 4245060 (P4/S5) poor garbage collector performance
#
# This message is just intended to work-around that problem.
# If printing should fail even so, the test will try to return
# the exit status 96 instead of 97 to indicate the problem.
# However, the test may fail or even crash on some platforms
# suffering the bug 4239841 or 4245060.
Failure: ExceptionInInitializerError: target class not found
Test failed.
----------System.err:(0/0)----------

Looks like it may have been a OOME during class loading.