<Beans Dev> Fwd: Re: [PATCH] test/jdk/java/beans/PropertyEditor/Test6397609.java failed in JITed code

Sergey Bylokhov Sergey.Bylokhov at oracle.com
Wed Jan 9 22:16:34 UTC 2019

On 08/01/2019 23:19, Alan Bateman wrote:
>> An existed tests in for beans which use OOM are run as tier3 tests, and as far as I know do not cause some unexpected failures?
>> If you do not suggest to rewrite an existed tests, then it will be better in this case to use the same solution.
> If someone has cycles then it would be good to cleanup the other tests too. You mentioned agentvm in one of your mails and that may be one motivation to avoid triggering OOME in random places.

Mention of "agentvm" mode was an example for why some of the corelibs tests works, since gc is triggered by some other tests and not as a result of System.gc(). If the tests uses OOM then it should set xmx which is not possible in agentvm mode, btw all client tests uses othervm.

Best regards, Sergey.

More information about the beans-dev mailing list