You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by Bruce Schuchardt <bs...@pivotal.io> on 2018/08/24 22:31:04 UTC

-PtestMaxParallelForks doesn't seem to work

I tried the new property that's supposed to let you limit the number of 
tests run in parallel and it didn't seem to work.

./gradlew -PtestMaxParallelForks=2 build

Instead of using half of my machine's CPUs this caused it to use all 8 
of them:

 > :geode-connectors:test > 96 tests completed
 > :geode-connectors:test > Executing test 
org.apache...internal.cli.JDBCCommandsAvailabilityTest
 > :geode-connectors:test > Executing test 
org.apache...internal.cli.DestroyMappingCommandFunctionTest
 > :geode-connectors:test > Executing test 
org.apache.geode.connectors.jdbc.JdbcWriterTest
 > :geode-connectors:test > Executing test 
org.apache.geode...jdbc.internal.AbstractJdbcCallbackTest
 > :geode-connectors:test > Executing test 
org.apache.geode...internal.cli.ListConnectionFunctionTest
 > :geode-connectors:test > Executing test 
org.apache.geode.connectors.jdbc.JdbcLoaderTest
 > :geode-connectors:test > Executing test 
org.apache...internal.cli.DescribeConnectionCommandTest
 > :geode-connectors:test > Executing test 
org.apache.geode.connectors.jdbc.JdbcAsyncWriterTest