On Tue, 30 May 2023 20:35:05 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
>
> Leonid Mesnik has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   more tests excluded.

I've been trying to figure out what 
java/util/concurrent/locks/Lock/OOMEInAQS.java
has to do with the deadlock bug, but I think I just got confused by using a 
single
bug ID to do the ProblemListings for more than one problem...

-------------

PR Comment: https://git.openjdk.org/jdk/pull/14193#issuecomment-1569079712

Reply via email to