curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-142) Make surefire forkCount configurable
Date Wed, 20 Aug 2014 18:06:26 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104248#comment-14104248
] 

ASF GitHub Bot commented on CURATOR-142:
----------------------------------------

GitHub user madrob opened a pull request:

    https://github.com/apache/curator/pull/40

    CURATOR-142 Make forkCount configurable

    Value can be set on the command line by invocing as:
    mvn test -Dsurefire-forkcount=4 # Or whatever number you like
    
    This closes #40

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/madrob/curator CURATOR-142

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #40
    
----
commit 72934da915db7722af73087b06a16f4c9de2b66a
Author: Mike Drob <mdrob@cloudera.com>
Date:   2014-08-20T18:05:06Z

    CURATOR-142 Make forkCount configurable
    
    Value can be set on the command line by invocing as:
    mvn test -Dsurefire-forkcount=4 # Or whatever number you like
    
    This closes #40

----


> Make surefire forkCount configurable
> ------------------------------------
>
>                 Key: CURATOR-142
>                 URL: https://issues.apache.org/jira/browse/CURATOR-142
>             Project: Apache Curator
>          Issue Type: Improvement
>            Reporter: Mike Drob
>            Assignee: Jordan Zimmerman
>             Fix For: 2.7.0
>
>
> When running unit tests, it would be nice if the parallelism was configurable. Running
with default settings takes about ~35 minutes on my laptop and I would like to reduce that.
> Tried it at 3, and the runtime was ~15 minutes. Tried it at 8 and got test failures.
We can leave the default at 1 for now, to make sure Jenkins doesn't see bad results, but eventually
it would be good to increase that as well to benefit new contributors.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message