RFR (S) 8230052: MLVM findDeadlock test timed out

[David Holmes]

On 29/08/2020 5:18 am, Coleen Phillimore wrote:
> 
> 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:

So no longer trying to fix it just trying to get more diagnostics. But 
how much logging info is that going to produce? Are we just going to hit 
the jtreg buffer limit?

I would have gone for some coarser higher-level "logging" initially. It 
is going to be hard to correlate the log entries with what is happening 
at the test level without output from the test itself that will appear 
in-order with the system logging. So I'm not at all sure this logging 
will really help.

But lets give it a try.

David

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