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

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on ZOOKEEPER-2198:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12736407/ZOOKEEPER-2198.001.patch
  against trunk revision 1682623.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 4 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2726//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2726//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2726//console

This message is automatically generated.

> 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)