RFR: 8289612: Change hotspot/jtreg tests to not use Thread.stop [v8]
David Holmes
dholmes at openjdk.org
Mon Jul 18 01:16:37 UTC 2022
On Sun, 17 Jul 2022 21:55:47 GMT, Leonid Mesnik <lmesnik at openjdk.org> wrote:
>> Looks like the test is using the default timeout value of 120 seconds/2 minutes.
>> With the usual timeoutFactor of 4 (or higher) used by Mach5, this should be
>> okay in that environment, but it might not be if invoked with a timeoutFactor
>> not set (which defaults to 1, IIRC).
>
> VM doesn't wait for the completion of threads that are executed native code. Seems like a new bug?
@lmesnik I don't understand what you mean here. The cHeapEater thread is a non-daemon thread so the test program won't terminate until it does. In the old code we would assist it to terminate early using stop() but in the new code it will run until it completes normally after 180 seconds.
-------------
PR: https://git.openjdk.org/jdk/pull/9505
More information about the hotspot-dev
mailing list