[DRILL-2039] use forks-per-CPU units in forkCount

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Component/s: Tools, Build & Test
• Assignee: Hanifi Gunes
• Reporter: Daniel Barclay
• Created: 19/Jan/15 21:10
• Updated: 14/May/15 23:18
• Resolved: 11/Apr/15 04:59

Description

Can Surefire's fork count be set using units of forks per CPU instead of the absolute number of forks (i.e., <forkCount>1C</forkCount> instead of <forkCount>4</forkcount>)?

That would let developers with more powerful machines still run tests in parallel while letting others avoid or reduce test timeout errors without the risk of forgetting to re-edit pom.xml after every switch to a different git branch.

Issue Links

• depends upon: DRILL-2685 Unique-ify local Hive metastore directory or unit test fails
• depends upon: DRILL-2733 Make dfs_test.tmp schema location on local fs exclusive to test JVM fork.