[DRILL-5893] Maven forkCount property is too aggressive causing builds to fail on some machines.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.12.0
• Labels: doc-impacting ready-to-commit
• Assignee: Timothy Farkas
• Reporter: Timothy Farkas
• Reviewer: Arina Ielchiieva
• Created: 19/Oct/17 17:51
• Updated: 23/Oct/17 18:39
• Resolved: 23/Oct/17 18:39

Description

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.

Issue Links

• links to: GitHub Pull Request #1003