RFR: 8308986: Disable svc tests failing with virtual thread factory
Daniel D. Daugherty
dcubed at openjdk.org
Tue May 30 20:06:59 UTC 2023
On Tue, 30 May 2023 19:51:04 GMT, Serguei Spitsyn <sspitsyn at 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/hotspot/jtreg/ProblemList-Virtual.txt line 35:
>
>> 33: serviceability/tmtools/jstack/DaemonThreadTest.java 8308033 generic-all
>> 34: vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java 8308985 generic-all
>> 35: vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java 8308985 generic-all
>
> I've closed the 8308985 as a dup of:
> [8308978](https://bugs.openjdk.org/browse/JDK-8308978) regression with a deadlock involving FollowReferences
> Should the 8308985 be replaced with the 8308978?
> There is already a tested fix for 8308978.
> Alex is going to post a PR today or tomorrow.
> Do we still want to problem-list these two tests?
Please switch from 8308985 to 8308978. I've also changed this bug
into a sub-task of 8308978 and bumped the priorities of both bugs
to P2. Regressions start at P2 and ProblemListing match the priority
of their parent bug.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/14193#discussion_r1210769143
More information about the serviceability-dev
mailing list