[
https://issues.apache.org/jira/browse/CURATOR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137267#comment-15137267
]
ASF GitHub Bot commented on CURATOR-302:
----------------------------------------
GitHub user dragonsinth opened a pull request:
https://github.com/apache/curator/pull/132
CURATOR-302: fix TestTreeCache.testKilledSession()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dragonsinth/curator CURATOR-302
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/132.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #132
----
commit 822890844a608caae20a7c7ce8b2b7aaa2b0f964
Author: Scott Blum <[email protected]>
Date: 2016-02-08T17:16:41Z
CURATOR-302: fix TestTreeCache.testKilledSession()
----
> TestTreeCache.testKilledSession() fails in 3.0 branch
> -----------------------------------------------------
>
> Key: CURATOR-302
> URL: https://issues.apache.org/jira/browse/CURATOR-302
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 3.1.0
> Reporter: Scott Blum
> Assignee: Scott Blum
>
> Jordan Zimmerman:
> {code}
> In this branch, TestTreeCache.testKilledSession() is failing at:
> assertEvent(TreeCacheEvent.Type.NODE_REMOVED, "/test/me",
> "data".getBytes());
> {code}
> However, if I change the two asserts to:
> {code}
> assertEvent(TreeCacheEvent.Type.INITIALIZED);
> assertEvent(TreeCacheEvent.Type.NODE_REMOVED, "/test/me",
> "data".getBytes());
> {code}
> it works.
> Scott:
> It's looking like some kind of internal behavior change in the framework.
> I'm going to have to add some tracing and compare the behaviors between trunk
> and 3.0 to uncover what changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
