[
https://issues.apache.org/jira/browse/DRILL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544534#comment-14544534
]
Venki Korukanti commented on DRILL-2039:
----------------------------------------
Few other devs also experienced the same recently. I think it is ok to revert
back to 4.
> use forks-per-CPU units in forkCount
> ------------------------------------
>
> Key: DRILL-2039
> URL: https://issues.apache.org/jira/browse/DRILL-2039
> Project: Apache Drill
> Issue Type: Improvement
> Components: Tools, Build & Test
> Reporter: Daniel Barclay (Drill)
> Assignee: Hanifi Gunes
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: DRILL-2039.1.patch.txt, DRILL-2039.2.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
