[
https://issues.apache.org/jira/browse/DRILL-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211447#comment-16211447
]
ASF GitHub Bot commented on DRILL-5893:
---------------------------------------
GitHub user ilooner opened a pull request:
https://github.com/apache/drill/pull/1003
DRILL-5893: Reverted the number of forked test processes back to 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilooner/drill DRILL-5893
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/1003.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1003
----
commit b036bcc9f3780613f0a2ead104112aa636cdbb6c
Author: Timothy Farkas <[email protected]>
Date: 2017-10-19T17:57:05Z
DRILL-5893: Reverted the number of forked test processes back to 2
----
> 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
> Reporter: Timothy Farkas
> Assignee: Timothy Farkas
>
> 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"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
