[
https://issues.apache.org/jira/browse/DRILL-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-5893:
------------------------------------
Labels: doc-impacting ready-to-commit (was: doc-impacting)
> 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"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
