[
https://issues.apache.org/jira/browse/CURATOR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709291#comment-14709291
]
Jordan Zimmerman commented on CURATOR-252:
------------------------------------------
That's the genesis of the Timing class. I've been trying to get the tests
repeatable for years. The problem is ZooKeeper itself. It simply doesn't behave
predictably. Getting more testing hooks into ZooKeeper would be good too. It
turns out that one of the hooks I wrote myself is going to be in 3.5. Hopefully
we can get more in.
> TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed
> -------------------------------------------------------------------
>
> Key: CURATOR-252
> URL: https://issues.apache.org/jira/browse/CURATOR-252
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Reporter: Mike Drob
> Priority: Blocker
>
> Running the full test suite locally, this test failed for me ~20% of the time.
> {noformat}
> java.lang.AssertionError: Callback has not been called expected [true] but
> found [false]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertTrue(Assert.java:42)
> at
> org.apache.curator.framework.recipes.leader.TestLeaderSelectorEdges.createProtectedNodeInBackgroundTest(TestLeaderSelectorEdges.java:189)
> {noformat}
> Unfortunately, I do not have full logs available at this time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
