[
https://issues.apache.org/jira/browse/DRILL-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215438#comment-16215438
]
ASF GitHub Bot commented on DRILL-5893:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/1003
> Maven forkCount property is too aggressive causing builds to fail on some
> machines.
> -----------------------------------------------------------------------------------
>
> Key: DRILL-5893
> URL: https://issues.apache.org/jira/browse/DRILL-5893
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.12.0
> Reporter: Timothy Farkas
> Assignee: Timothy Farkas
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.12.0
>
>
> In DRILL-5752 I changed the forkCount parameter from "2" to "1C". This
> changed the number of test process spawned from 2 test processes to 1 test
> process per core on the machine. This worked fine on dev laptops and jenkins
> servers, but large build machines (32 cores) can get slowed down by all the
> test processes resulting in tests timing out. Also spawning so many test
> processes can also aggravate the issue described in DRILL-5890.
> For this jira I will revert the default for forkCount back to "2"
> *For documentation*
> https://drill.apache.org/docs/apache-drill-contribution-guidelines/
> For these line {{Contributions should pass existing unit tests.}} we may add
> that developer should have successful build using {{mvn clean install}}, to
> speed up unit tests {{mvn clean install -DforkCount=1C}} can be used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
