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

Hudson commented on ZOOKEEPER-1353:
-----------------------------------

Integrated in ZooKeeper-trunk #1451 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/1451/])
    ZOOKEEPER-1353. C client test suite fails consistently. (Clint Byrum via 
mahadev)

mahadev : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1240905
Files : 
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/c/tests/TestZookeeperInit.cc

                
> C client test suite fails consistently
> --------------------------------------
>
>                 Key: ZOOKEEPER-1353
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1353
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client, tests
>    Affects Versions: 3.3.4
>         Environment: Ubuntu precise (dev release), amd64
>            Reporter: Clint Byrum
>            Assignee: Clint Byrum
>            Priority: Minor
>              Labels: patch, test
>             Fix For: 3.3.5, 3.4.3, 3.5.0
>
>         Attachments: fix-broken-c-client-unittest.patch, 
> fix-broken-c-client-unittest.patch
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> When the c client test suite, zktest-mt, is run, it fails with this:
> tests/TestZookeeperInit.cc:233: Assertion: equality assertion failed 
> [Expected: 2, Actual  : 22]
> This was also reported in 3.3.1 here:
> http://www.mail-archive.com/zookeeper-dev@hadoop.apache.org/msg08914.html
> The C client tests are making some assumptions that are not valid. 
> getaddrinfo may have, at one time, returned ENOENT instead of EINVAL for the 
> host given in the test. The assertion should simply be that EINVAL | ENOENT 
> are given, so that builds on platforms which return ENOENT for this are not 
> broken.

--
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

        

Reply via email to