You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/05/31 07:55:17 UTC

[jira] [Updated] (ZOOKEEPER-2198) Set default test.junit.threads to 1.

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated ZOOKEEPER-2198:
-------------------------------------
    Summary: Set default test.junit.threads to 1.  (was: Set default test,junit.threads to 1.)

> Set default test.junit.threads to 1.
> ------------------------------------
>
>                 Key: ZOOKEEPER-2198
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2198
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: build
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>             Fix For: 3.5.1, 3.6.0
>
>         Attachments: ZOOKEEPER-2198.001.patch
>
>
> Some systems are seeing test failures under concurrent execution.  This issue proposes to change the default {{test.junit.threads}} to 1 so that those environments continue to get consistent test runs.  Jenkins and individual developer environments can set multiple threads with a command line argument, so most environments will still get the benefit of faster test runs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)