On Sat, 27 May 2023 20:21:46 GMT, Leonid Mesnik <lmes...@openjdk.org> wrote:
> Disable test > java/util/concurrent/locks/Lock/OOMEInAQS.java > Test provokes OOME and might catch it in an unexpected location. It looks > like an issue similar to https://bugs.openjdk.org/browse/JDK-8298066. > However, generally the OOME might be thrown mount/umount or in unparker > thread. There are no plans to fix such tests to be able to pass with virtual > threads now. > > Also, disable > mTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java > vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java > because of https://bugs.openjdk.org/browse/JDK-8308985 test/jdk/ProblemList-Virtual.txt line 75: > 73: java/lang/invoke/condy/CondyNestedResolutionTest.java 0000000 generic-all > 74: java/lang/ref/OOMEInReferenceHandler.java 0000000 generic-all > 75: java/util/concurrent/locks/Lock/OOMEInAQS.java 0000000 generic-all The comment a bit further to see where it explains why this section uses "0000000" for the JBS issue. There's a few typos in the text, e.g. "with with" and "test migth". It might be useful to make that text a bit clearer as I'm sure there will be questions on why there aren't JBS issues for tests excluded from running this mode. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/14193#discussion_r1208346103
