curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-302) TestTreeCache.testKilledSession() fails in 3.0 branch
Date Mon, 08 Feb 2016 17:19:39 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137271#comment-15137271
] 

ASF GitHub Bot commented on CURATOR-302:
----------------------------------------

Github user Randgalt commented on the pull request:

    https://github.com/apache/curator/pull/132#issuecomment-181483569
  
    LGTM


> 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
>             Fix For: 3.1.0
>
>
> 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)

Mime
View raw message