[ https://issues.apache.org/jira/browse/ZOOKEEPER-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414186#comment-15414186 ]
Hadoop QA commented on ZOOKEEPER-2508: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12822871/ZOOKEEPER-2508-04.patch against trunk revision 1755379. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 74 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/3345//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3345//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3345//console This message is automatically generated. > Many ZooKeeper tests are flaky because they proceed with zk operation without > connecting to ZooKeeper server. > ------------------------------------------------------------------------------------------------------------- > > Key: ZOOKEEPER-2508 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2508 > Project: ZooKeeper > Issue Type: Bug > Components: tests > Reporter: Arshad Mohammad > Assignee: Arshad Mohammad > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-2508-01.patch, ZOOKEEPER-2508-02.patch, > ZOOKEEPER-2508-03.patch, ZOOKEEPER-2508-04.patch > > > Many ZooKeeper tests are flaky because they proceed with zk operation without > connecting to ZooKeeper server. > Recently in our build > {{org.apache.zookeeper.server.ZooKeeperServerMainTest.testStandalone()}} > failed. > After analyzing we found that it is failed because it is not waiting for > ZooKeeper client get connected to server. In this case normally zookeeper > client gets connected immediately but if not connected immediately the test > case is bound to fail. > Not only ZooKeeperServerMainTest but there are many other classes which have > such test cases. This jira is to address all those test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)