[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: 8231294: ZGC: vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted002 fails
From:       "Daniel D. Daugherty" <daniel.daugherty () oracle ! com>
Date:       2019-09-26 18:20:23
Message-ID: 585efd40-6870-743b-d1b3-ed176c3a73c4 () oracle ! com
[Download RAW message or body]

Just figured you might want to know that the heap size change was 
happening... :-)

Dan

On 9/26/19 2:06 PM, serguei.spitsyn@oracle.com wrote:
> Dan, thank you for adding the serviceability-dev mailing list.
> It looks good but has been already pushed. :)
>
> Thanks,
> Serguei
>
>
> On 9/26/19 07:28, Daniel D. Daugherty wrote:
>> Just for the record... JVM/TI belongs to the Serviceability Team
>> so I've added serviceability-dev@...
>>
>> However, the Runtime team and Serviceability team quite often tag
>> team on JVM/TI issues and lurk on each other's aliases...
>>
>> Dan
>>
>>
>> On 9/26/19 3:14 AM, Per Liden wrote:
>>> (CC:ing hotspot-runtime-dev, as the test belongs to runtime)
>>>
>>> On 9/25/19 10:57 AM, Per Liden wrote:
>>>> The resexhausted002 test uses an 8M heap, which is a bit too small 
>>>> for ZGC. Bumping it to 128M to allow the test to pass on ZGC too.
>>>>
>>>> Bug: https://bugs.openjdk.java.net/browse/JDK-8231294
>>>> Webrev: http://cr.openjdk.java.net/~pliden/8231294/webrev.0
>>>>
>>>> Testing: Manual testing with G1 and ZGC
>>>>
>>>> /Per
>>
>

[prev in list] [next in list] [prev in thread] [next in thread]