curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <>
Subject [jira] [Commented] (CURATOR-142) Make surefire forkCount configurable
Date Wed, 20 Aug 2014 21:33:26 GMT


Mike Drob commented on CURATOR-142:

Yes, it consistently passes with {{3}} and failed once with {{8}} for me. I have not tried
numbers in between. For the scope of this JIRA, I think we should just make it easily configurable
from the command line while leaving the default value at {{1}}, and then worry about setting
it to a higher value later.

> Make surefire forkCount configurable
> ------------------------------------
>                 Key: CURATOR-142
>                 URL:
>             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

View raw message