RFR 8230055: ModuleStressGC.java times out on Win*

[coleen.phillimore at oracle.com]

I had a look at the artifacts from the failed run, and there's no good 
information to tell why the test stopped for 40 minutes (both on 
windows).  It could have been swapped out.

Reducing the loop count so that we verify what the test intends to 
verify makes sense to me.  It'll run faster on all platforms.

I think this change looks fine.

Coleen

On 11/8/19 7:59 AM, Harold Seigel wrote:
> Thanks Leonid.
>
> I'll withdraw the webrev.
>
> Harold
>
> On 11/7/2019 11:32 PM, Leonid Mesnik wrote:
>> Hi
>>
>> I am not sure that it is a good idea. The bug says that test times 
>> out and take more 40 minutes.
>>
>> However usually it takes less than 2 minutes to complete test (on any 
>> platform). So I think that it is not just a long test but rather some 
>> outlier which should be investigated.
>>
>> Leonid
>>
>> On 11/7/19 2:03 PM, Harold Seigel wrote:
>>> Hi,
>>>
>>> Please review this small change to help prevent test 
>>> runtime/modules/ModuleStress/ModuleStressGC.java from timing out. 
>>> The change reduces the number of loop iterations in the test by 40%.
>>>
>>> Open Webrev: 
>>> http://cr.openjdk.java.net/~hseigel/bug_8230055/webrev/index.html
>>>
>>> JBS Bug: https://bugs.openjdk.java.net/browse/JDK-8230055
>>>
>>> The change was tested by running Mach5 tier2 tests on Linux-x64, 
>>> Solaris, Windows, and Mac OS X.
>>>
>>> Thanks, Harold
>>>