[ https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931554#comment-15931554 ]
ASF GitHub Bot commented on ZOOKEEPER-2722: ------------------------------------------- Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/191 @skamille OK, for some reasons I can't even get a single repro with this patch now on Apache Jenkins. I've kicked 10+ builds on apache jenkins and all of them pass this test. Unfortunately the link I posted earlier use a version of patch that does have instrumented logs so I can't tell the state of ZK when weird thing happened. I think we can commit this if this patch is OK with you, and let it hammered by daily builds / other pre-commit jobs so we can gather more log data on the contexts when it reproduces. > Flaky Test: > org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment > ------------------------------------------------------------------------------- > > Key: ZOOKEEPER-2722 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722 > Project: ZooKeeper > Issue Type: Bug > Components: tests > Affects Versions: 3.4.9, 3.5.2 > Reporter: Michael Han > Assignee: Michael Han > Labels: flaky, flaky-build, flaky-test > Fix For: 3.5.3, 3.6.0 > > > {noformat} > Error Message > KeeperErrorCode = ConnectionLoss for /test > Stacktrace > org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode > = ConnectionLoss for /test > at org.apache.zookeeper.KeeperException.create(KeeperException.java:99) > at org.apache.zookeeper.KeeperException.create(KeeperException.java:51) > at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423) > at > org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238) > at > org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.lang.Thread.run(Thread.java:745) > {noformat} > Looks like we should retry before giving up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)