[
https://issues.apache.org/jira/browse/ZOOKEEPER-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566480#comment-14566480
]
Hudson commented on ZOOKEEPER-2198:
-----------------------------------
ABORTED: Integrated in ZooKeeper-trunk #2708 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2708/])
ZOOKEEPER-2198 Set default test.junit.threads to 1 (Chris Nauroth via michim)
(michim:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1682701)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
* /zookeeper/trunk/src/java/test/bin/test-patch.sh
> 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)
