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

[Sergey Bylokhov]

On 29.06.16 11:18, Semyon Sadetsky wrote:
> Is it the case for a 250 GB RAM server only?
> I think Util.generateOOME() should be improved in any case, to prevent
> future tests to be slowdown/failed if running on large RAM servers.

The flood of so much memory is incorrect behavior for the tests which 
tries to test some memory leaks. and it is a good thing that they are 
fails if tries to do this.

>>
>>>
>>> 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?
> bug6795356.java

Covered by the fix.

> TwentyThousandTest.java

already have -mx option.

> WindowsLeak.java

already have -mx option.

>
> To find them all you can search for Util.generateOOME() usages

good to know.

>
> --Semyon
>>
>>> 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.