[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621839#action_12621839
 ] 

Flavio Paiva Junqueira commented on ZOOKEEPER-111:
--------------------------------------------------

Now both SyncCallTest and WatcherFuncTest are failing on 
ClientBase.recursiveDelete. Here are the reported messages:

{noformat}
junit.framework.AssertionFailedError: delete
        at 
org.apache.zookeeper.test.ClientBase.recursiveDelete(ClientBase.java:168)
        at org.apache.zookeeper.test.ClientBase.tearDown(ClientBase.java:158)
        at 
org.apache.zookeeper.test.WatcherFuncTest.tearDown(WatcherFuncTest.java:101)
{noformat}

> significant cleanup of existing tests
> -------------------------------------
>
>                 Key: ZOOKEEPER-111
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-111
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>         Attachments: TEST-org.apache.zookeeper.test.AsyncTest.txt, 
> ZOOKEEPER-111.patch, ZOOKEEPER-111.patch, ZOOKEEPER-111.patch
>
>
> About to submit a patch that significantly cleans up existing tests.
> 1) removed the need for "sleep" calls in the tests, instead I monitor the 
> status of the server (using the client socket "stat" command) which provides 
> a barrier to the client test operations. I use this barrier both when 
> starting and ending the test.
> 2) also fixed a number of problems in the tests where the test itself was 
> broken.
> 3) general cleanup and some refactoring to make it easier to write new tests, 
> maintain old, and track down issues if the test does find a problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to