You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Thomas Koch (Created) (JIRA)" <ji...@apache.org> on 2011/10/26 16:25:32 UTC

[jira] [Created] (ZOOKEEPER-1254) test correct watch handling with multi ops

test correct watch handling with multi ops
------------------------------------------

                 Key: ZOOKEEPER-1254
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1254
             Project: ZooKeeper
          Issue Type: Improvement
            Reporter: Thomas Koch
            Assignee: Thomas Koch


I was wondering, what happens with watches that would be triggered by a multi op if subsequent ops fail. I didn't find a test for this, wrote one and everything was fine. :-)

The patch contains two additional test cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (ZOOKEEPER-1254) test correct watch handling with multi ops

Posted by "Thomas Koch (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Koch updated ZOOKEEPER-1254:
-----------------------------------

    Attachment: ZOOKEEPER-1254.patch
    
> test correct watch handling with multi ops
> ------------------------------------------
>
>                 Key: ZOOKEEPER-1254
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1254
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Thomas Koch
>            Assignee: Thomas Koch
>         Attachments: ZOOKEEPER-1254.patch
>
>
> I was wondering, what happens with watches that would be triggered by a multi op if subsequent ops fail. I didn't find a test for this, wrote one and everything was fine. :-)
> The patch contains two additional test cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (ZOOKEEPER-1254) test correct watch handling with multi ops

Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136025#comment-13136025 ] 

Hadoop QA commented on ZOOKEEPER-1254:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12500886/ZOOKEEPER-1254.patch
  against trunk revision 1188523.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/683//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/683//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/683//console

This message is automatically generated.
                
> test correct watch handling with multi ops
> ------------------------------------------
>
>                 Key: ZOOKEEPER-1254
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1254
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Thomas Koch
>            Assignee: Thomas Koch
>         Attachments: ZOOKEEPER-1254.patch
>
>
> I was wondering, what happens with watches that would be triggered by a multi op if subsequent ops fail. I didn't find a test for this, wrote one and everything was fine. :-)
> The patch contains two additional test cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (ZOOKEEPER-1254) test correct watch handling with multi ops

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136959#comment-13136959 ] 

Hudson commented on ZOOKEEPER-1254:
-----------------------------------

Integrated in ZooKeeper-trunk #1346 (See [https://builds.apache.org/job/ZooKeeper-trunk/1346/])
    ZOOKEEPER-1254. test correct watch handling with multi ops (Thomas Koch via phunt)

phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189310
Files : 
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/MultiTransactionTest.java

                
> test correct watch handling with multi ops
> ------------------------------------------
>
>                 Key: ZOOKEEPER-1254
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1254
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Thomas Koch
>            Assignee: Thomas Koch
>         Attachments: ZOOKEEPER-1254.patch
>
>
> I was wondering, what happens with watches that would be triggered by a multi op if subsequent ops fail. I didn't find a test for this, wrote one and everything was fine. :-)
> The patch contains two additional test cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira