RFR: 8191768 - Introduce a concurrency factor to be able to scale up or down jtreg concurrency when running Hotspot tests

[Christian Tornqvist]

> On Nov 29, 2017, at 2:22 AM, David Holmes <david.holmes at oracle.com> wrote:
> 
> Catching up after mini-vacation ...
> 
> On 23/11/2017 2:47 AM, Christian Tornqvist wrote:
>> Please review this small change that allows a user to scale up or down the concurrency for running Hotspot jtreg tests using CONCURRENCY_FACTOR.
>> Webrev: http://cr.openjdk.java.net/~ctornqvi/webrev/8191768/webrev.00/ <http://cr.openjdk.java.net/~ctornqvi/webrev/8191768/webrev.00/>
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8191768 <https://bugs.openjdk.java.net/browse/JDK-8191768>
> 
> So setting CONCURRENCY_FACTOR = 0 will ensure no concurrent tests will run?

It would, but you should probably just set CONCURRENCY=1 instead 

> 
> Are we guaranteed that the higher-level testing framework will only run one jtreg test job per system at a time?
> 
> Thanks,
> David
> 
>> Thanks,
>> Christian