You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hongchao Deng (JIRA)" <ji...@apache.org> on 2015/03/11 22:03:39 UTC

[jira] [Commented] (ZOOKEEPER-2138) ZooKeeper C client testing is failing

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

Hongchao Deng commented on ZOOKEEPER-2138:
------------------------------------------

[~michim], can you take a look?

I also suggest that if zktest-st failed, we don't need to run zktest-mt. How to do it?

> ZooKeeper C client testing is failing
> -------------------------------------
>
>                 Key: ZOOKEEPER-2138
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2138
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Hongchao Deng
>             Fix For: 3.6.0
>
>
> After testHammer has been fixed, now test-core-java is successful and test-core-cppunit emerges to fail:
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2624/console
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/2557/console
> I have try git bitsect and figure out two JIRAs causing problems:
> * ZOOKEEPER-2073
> My local jenkins showed the error messages:
> {code}
>  [exec] /var/lib/jenkins/workspace/zk-trunk/src/c/tests/TestClient.cc:1072: Assertion: assertion failed [Expression: ctx.waitForConnected(zk)]
> {code}
> * ZOOKEEPER-2079
> After resetting ZK-2073, I also got the error (not always):
> {code}
> [exec] /var/lib/jenkins/workspace/zk-trunk/src/c/tests/zkServer.sh: line 62: kill: (4703) - No such process
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)