RFR: JDK-8286789: Test forceEarlyReturn002.java timed out [v2]

David Holmes dholmes at openjdk.org
Mon Aug 21 05:05:26 UTC 2023


On Wed, 16 Aug 2023 02:33:44 GMT, Alex Menkov <amenkov at openjdk.org> 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 finished testing and performs cleanup process (debugger sends debuggee a command to exit, but debuggee doesn't receive the command).
>> This is the only test which has this intermittent communication failures.
>> The test was problem-listed, I was not able to reproduce the issue with 1000+ runs.
>> 
>> Debuggee creates a thread which executes tight infinite loop in native code (in "virtual thread factory" mode it's pinned virtual thread).
>> The fix adds delays in the loop and adds new command to exit from native method after testing.
>> 
>> Testing: 100 runs in "virtual thread factory" mode on all Oracle supported platforms.
>
> Alex Menkov has updated the pull request incrementally with one additional commit since the last revision:
> 
>   use atomic instead of volatile

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.

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

PR Comment: https://git.openjdk.org/jdk/pull/15301#issuecomment-1685646376


More information about the serviceability-dev mailing list