[
https://issues.apache.org/jira/browse/DRILL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487998#comment-14487998
]
Venki Korukanti commented on DRILL-2039:
----------------------------------------
With 1C setting on top of DRILL-2685 and DRILL-2733 patches, I ran "mvn clean
install" on two VMs and my Macbook several times. Few other devs also ran the
queries. I have seen timeouts few times for tests TestWriteToDisk and
TestLargeFileComplication which are known to take more than than the other
tests. Increased the timeouts a little bit for these tests as part of
DRILL-2733 and ran tests again. No timeouts so far.
If any devs experiencing timeouts and want to lower the forkCount, there is
only one place (root pom.xml) where they have to modify the forkCount. (Tried
finding a way to set forkCount from command line, but couldn't find any.
-DforkCount=4 didn't work. If anyone know how to change forkCount from command
line, please post it here)
I think v2 patch is ready to go. +1.
> 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: Venki Korukanti
> 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)
