RFR (S) 8230052: MLVM findDeadlock test timed out

[Coleen Phillimore]

On 8/27/20 7:59 PM, Ioi Lam wrote:
> Hi Coleen,
>
> From the comments of the bug, it looks like we are still not sure 
> whether this happened because we're just running on a slow machine, or 
> whether there's is an real underlying issue.

Thanks for looking at this.  We don't know whether there's an issue 
unless we download all the artifacts and debug the core file.  In the 
one that failed, we did that and there was nothing wrong.  It was busy 
doing GC.  Honestly don't know what we're looking for if there's an 
underlying issue.
>
> Since the test fails very rarely (a few times a year??), if we are 
> modifying it, maybe print out time stamps after every iteration? So if 
> this fails again in six months we will have more info to look at. 
> E.g., if the time stamps are well spaced out, we know we're running on 
> a slow machine. If the time stamps get progressively longer, we 
> probably have a bug in the test or in the VM.

That's a good idea.  I see David below has a suggestion, which is good!

Coleen

>
> Thanks
> - Ioi
>
> On 8/27/20 3: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
>>
>> Ran test 100x with < 1minute run time.  Should I add a timeout of 10 
>> minutes also?
>>
>> Thanks,
>> Coleen
>