RFR (S) 8230052: MLVM findDeadlock test timed out

Coleen Phillimore coleen.phillimore at oracle.com
Fri Aug 28 19:18:09 UTC 2020


Continuing the discussion in the bug, I've taken out the System.gc() and 
added -Xlog:gc+safepoint to see if these give any ideas why the test 
times out. See:

bug link https://bugs.openjdk.java.net/browse/JDK-8230052
open webrev at http://cr.openjdk.java.net/~coleenp/2020/8230052.02/webrev

thanks,
Coleen


On 8/28/20 8:22 AM, Patricio Chilano wrote:
> Hi Coleen,
>
> On 8/27/20 7:53 PM, Coleen Phillimore wrote:
>> Summary: Add a System.gc() and reduce iteration count for more 
>> stability.
>>
>> open webrev at 
>> http://cr.openjdk.java.net/~coleenp/2020/8230052.01/webrev
>> bug link https://bugs.openjdk.java.net/browse/JDK-8230052
> Looks good to me.
> If we see any new failure I think we can try to run the test with 
> extra VM logging enabled.
>
>
> Thanks,
> Patricio
>> Ran test 100x with < 1minute run time. Should I add a timeout of 10 
>> minutes also?
>>
>> Thanks,
>> Coleen
>



More information about the hotspot-runtime-dev mailing list