RFR(S) 8009585: [TESTBUG] test/runtime/7196045 times out

David Holmes david.holmes at oracle.com
Wed Jul 31 17:48:52 PDT 2013


On 1/08/2013 6:26 AM, Christian Tornqvist wrote:
> Did a jprt run with both tests (increased the jtreg timeout on the original
> test for 7196045 to 200 seconds), both reproduced on 30/30 targets (all
> platforms except embedded). Test fails to run on embedded since the counter
> isn't there. This should be solved by excluding this test on embedded
> platforms since it's not applicable there.

The test needs to add -XX:+UsePerfData in that case.

David
-----

>
> Thanks,
> Christian
>
> -----Original Message-----
> From: David Holmes [mailto:david.holmes at oracle.com]
> Sent: den 29 juli 2013 00:46
> To: Christian Tornqvist
> Cc: hotspot-runtime-dev at openjdk.java.net
> Subject: Re: RFR(S) 8009585: [TESTBUG] test/runtime/7196045 times out
>
> On 26/07/2013 6:44 AM, Christian Tornqvist wrote:
>> Small fix for a timeout issue in test/runtime/7196045, the internal
>> test timeout was set to 120 seconds which is the same default timeout
>> used by jtreg. Usually meant that jtreg ended up killing the test
>> before it finished. Added an allocation thread and decreased the heap
>> size, this has greatly increased the reproduction rate of this test,
>> reproduces within one second for 20 out of 20 runs. Decreased the run
>> time of the test from 120 seconds to 10 seconds.
>
> Did you see a similar reproduction rate on all platforms? This test might
> always trivially pass on slower/smaller devices.
>
> David
> -----
>
>> Webrev:
>>
>> http://cr.openjdk.java.net/~ctornqvi/webrev/8009585/webrev.00/
>>
>> Bug:
>>
>> http://bugs.sun.com/view_bug.do?bug_id=8009585
>>
>> Thanks,
>>
>> Christian
>>
>


More information about the hotspot-runtime-dev mailing list