[
https://issues.apache.org/jira/browse/CURATOR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709289#comment-14709289
]
Mike Drob commented on CURATOR-252:
-----------------------------------
When there are timing related failures, then we can simulate the relevant
sequencing by adding strategically placed debug latches. I think it's still a
good idea to have separate issues for separate tests, and we can close them as
duplicates later if they turn out to have the same cause.
Using a parent JIRA and creating sub-tasks makes sense too.
> 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)
