RFR: 8191768 - Introduce a concurrency factor to be able to scale up or down jtreg concurrency when running Hotspot tests
Erik Joelsson
erik.joelsson at oracle.com
Wed Nov 29 17:47:31 UTC 2017
On 2017-11-28 23:22, David Holmes 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?
>
> Are we guaranteed that the higher-level testing framework will only
> run one jtreg test job per system at a time?
AFAIK yes. We only run one agent per system, and each agent only runs
one task at a time. (VMs on a physical host are usually over-allocated
on CPUs though so we cannot guarantee available CPU resources to each VM)
/Erik
>
> Thanks,
> David
>
>> Thanks,
>> Christian
>>
More information about the build-dev
mailing list