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

Alex Menkov amenkov at openjdk.java.net
Fri Nov 6 00:31:56 UTC 2020


On Wed, 4 Nov 2020 21:44:09 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

> 
> 
> > Had to implement runtime check (instead of using @requires) because resexhausted001 is also called by resexhausted004.
> 
> So does that mean you do or don't want resexhausted004 disabled on windows? If yes, there's no reason why you can't use @requires in the TestDescriptions.java for each of these tests (although I have no objecting to the runtime check). If no then you have a bug because you are disabling resexhausted004 on windows, and should use @requires in TestDescriptions.java for resexhausted001 instead.

resexhausted004 calls resexhausted001-003 (their run method) in random order (to ensure we can get several ResourceExhausted events)
I don't want to disable resexhausted004 on Windows completely, just skip resexhausted001

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

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


More information about the serviceability-dev mailing list