From bcf5f4648670770b6c5fcfd56fd24660fae5ad44 Mon Sep 17 00:00:00 2001
From: Maximilian Michels <mxm@apache.org>
Date: Wed, 1 Jun 2016 15:11:29 +0200
Subject: [PATCH] [FLINK-3607] decrease default forkCount for tests

This makes running test locally a more pleasant experience. It still
uses all exposed CPU cores (virtual or real). A custom forkCount can be
set using the flink.forkCount property, e.g. -Dflink.forkCount=4.
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index 6f444b3fdf067..23f6dc540473e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -89,7 +89,7 @@ under the License.
 		<!-- Need to use a user property here because the surefire
 			 forkCount is not exposed as a property. With this we can set
 			 it on the "mvn" commandline in travis. -->
-		<flink.forkCount>1.5C</flink.forkCount>
+		<flink.forkCount>1C</flink.forkCount>
 		<flink.reuseForks>true</flink.reuseForks>
 		<log4j.configuration>log4j-test.properties</log4j.configuration>
 		<slf4j.version>1.7.7</slf4j.version>