Integrated: 8254864: vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted001/TestDescription.java timed out

[Alex Menkov]

On Tue, 3 Nov 2020 23:16:50 GMT, Alex Menkov <amenkov at openjdk.org> wrote:

> - Fixed synchronization logic in resexhausted001;
> - On Windows JVM cannot produce OOM caused by thread creation failure. Massive thread creation causes big system (not VM) memory consumption, as a result test host dramatically slows down up to hang. Specifying small heap size we can get RESOURCE_EXHAUSTED_JAVA_HEAP, but this is not the goal of resexhausted001.
> So I disabled resexhausted001 on Windows.
> Had to implement runtime check (instead of using @requires) because resexhausted001 is also called by resexhausted004.
> - Additionally resexhausted001-resexhausted003 test were improved to verify JVMTI generates ResourceExhausted event with correct flag.

This pull request has now been integrated.

Changeset: a9dff942
Author:    Alex Menkov <amenkov at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/a9dff942
Stats:     47 lines in 6 files changed: 26 ins; 1 del; 20 mod

8254864: vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted001/TestDescription.java timed out

Reviewed-by: sspitsyn, cjplummer

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

PR: https://git.openjdk.java.net/jdk/pull/1046