zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-08-09 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/master 31501b8ab -> e104175bb ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode This is the third time this failure has popped up. This time it seemed to only impact tests run using NettyServerCnxnFactory

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-08-09 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/branch-3.5 d7c26e33f -> 23962f123 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode This is the third time this failure has popped up. This time it seemed to only impact tests run using NettyServerCnxnFac

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-30 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/branch-3.4 677b5ccb7 -> 4638b5585 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode See https://github.com/apache/zookeeper/pull/286 for description. Author: Abraham Fine Reviewers: Michael Han Closes

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-30 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/master a0eba7abd -> eab6e7a13 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode As hanm noticed and mentioned on the JIRA this flaky test can still fail. The reason is that we can reconnect before calling

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-30 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/branch-3.5 749b6024b -> 74e45a0d6 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode As hanm noticed and mentioned on the JIRA this flaky test can still fail. The reason is that we can reconnect before cal

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-15 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/branch-3.4 ac5fa3f54 -> 83e0ab896 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode On branch 3.4 we attempt to check that an invalid opcode in a request causes the server to disconnect the client with:

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-15 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/master 77ceace94 -> c38febe2d ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode On branch 3.5, testNonExistingOpCode appears to always take 30 seconds to execute (far too long): https://builds.apache.org

zookeeper git commit: ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode

2017-06-15 Thread hanm
Repository: zookeeper Updated Branches: refs/heads/branch-3.5 20dafe7be -> c89784cc5 ZOOKEEPER-2786: Flaky test: org.apache.zookeeper.test.ClientTest.testNonExistingOpCode On branch 3.5, testNonExistingOpCode appears to always take 30 seconds to execute (far too long): https://builds.apache