<Swing Dev> [9] Review Request: 8159899 [TEST_BUG] Timeout in tests when OOM should be generated

Sergey Bylokhov Sergey.Bylokhov at oracle.com
Tue Jun 28 12:51:42 UTC 2016


On 28.06.16 12:49, Semyon Sadetsky wrote:
> It seems the root cause is in the Util.generateOOME() method from the
> regtesthelpers library. It should take into account the heap maximum
> limit to generate OOME in a reasonable time.

The root cause is that the tests tries to allocate more than 250 GB of 
memory, I do not see the reason why it should do it, since 128m is 
enough for them.

>
> This utility method is used in other tests which are not covered by the
> fix but may fail due to the same reason.

Which one?

> On 6/27/2016 6:25 PM, Sergey Bylokhov wrote:
>> Hello.
>> Please review the fix for jdk9.
>>
>> Some of our tests fails with timeout when they tries to generate OOM.
>> This occur on the systems which have huge number of memory.
>>
>> In the fix I added "-xm" option to minimize the available amount of
>> memory.
>>
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8159899
>> Webrev can be found at:
>> http://cr.openjdk.java.net/~serb/8159899/webrev.00
>>
>


-- 
Best regards, Sergey.



More information about the swing-dev mailing list