On Mon, 21 Aug 2023 05:03:06 GMT, David Holmes wrote:
> Infinite loops are not good to have so the test adjustment seems fine in that
> regard. But I can't see how using the virtual thread factory could trigger a
> problem with this code.
It's not clear to me as well.
Debugger sends 'quit' com
On Wed, 16 Aug 2023 02:33:44 GMT, Alex Menkov wrote:
>> This is an attempt to fix suspicious code in the forceEarlyReturn002.java
>> and un-problemlist it to see if the problem appear again.
>>
>> The test fails in "virtual thread factory" mode with timeout for unclear
>> reason after it finis
On Wed, 16 Aug 2023 02:33:44 GMT, Alex Menkov wrote:
>> This is an attempt to fix suspicious code in the forceEarlyReturn002.java
>> and un-problemlist it to see if the problem appear again.
>>
>> The test fails in "virtual thread factory" mode with timeout for unclear
>> reason after it finis
On Wed, 16 Aug 2023 02:33:44 GMT, Alex Menkov wrote:
>> This is an attempt to fix suspicious code in the forceEarlyReturn002.java
>> and un-problemlist it to see if the problem appear again.
>>
>> The test fails in "virtual thread factory" mode with timeout for unclear
>> reason after it finis
> This is an attempt to fix suspicious code in the forceEarlyReturn002.java and
> un-problemlist it to see if the problem appear again.
>
> The test fails in "virtual thread factory" mode with timeout for unclear
> reason after it finished testing and performs cleanup process (debugger sends
>
On Wed, 16 Aug 2023 00:10:46 GMT, Leonid Mesnik wrote:
>> Alex Menkov has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> use atomic instead of volatile
>
> test/hotspot/jtreg/vmTestbase/nsk/jdwp/ThreadReference/ForceEarlyReturn/forceEarlyRe
