RFR: (XS): JDK-8213457: serviceability/sa/ClhsdbInspect.java time out

Jini George jini.george at oracle.com
Thu Jan 3 18:45:26 UTC 2019


Missed mentioning that I think this should be a good number considering 
that the max I have seen for this test is about 12 minutes and there is 
a safe buffer of about 20 more minutes.

Thanks!
Jini.

On 1/3/2019 11:56 PM, Jini George wrote:
> Thank you very much, Chris, for taking a look. I will modify the timeout 
> value to be 480 ==> 8 minutes ==> 32 minutes for tier1. Sounds good ?
> 
> Thanks!
> Jini.
> 
> On 1/3/2019 9:54 PM, Chris Plummer wrote:
>> Hi Jini,
>>
>> 2400 seems excessive. That's 40 minutes, which translates to 160 
>> minutes for our test runs. Did you mean timeout=240? It looks like a 
>> few of the Clhsdb tests were given large timeouts that are probably 
>> much more than is needed.
>>
>> thanks,
>>
>> Chris
>>
>> On 1/2/19 6:51 PM, Jini George wrote:
>>> Hello!
>>>
>>> Requesting reviews for a small fix for fixing the timeout failures of 
>>> the test: ClhsdbInspect.java by increasing the timeout value.
>>>
>>> BugID: https://bugs.openjdk.java.net/browse/JDK-8213457
>>> Webrev: http://cr.openjdk.java.net/~jgeorge/8213457/webrev.00/index.html
>>>
>>> The fix has been tested with about 200 repeated runs on windows post 
>>> this fix. The timeout was not observed.
>>>
>>> Thanks,
>>> Jini.
>>>
>>>
>>>
>>


More information about the serviceability-dev mailing list