[
https://issues.apache.org/jira/browse/ZOOKEEPER-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264944#comment-17264944
]
Norbert Kalmár commented on ZOOKEEPER-4049:
-------------------------------------------
Thanks [~ztzg], nice work!
Why wouldn't adding the configs to the docker config json work? Host machine
needs some sort of ipv6 support I guess? Like being able to get ipv6 address
itself?
Sorry, this might be a trivial question. Anyway, that would be the best
solution.
Either way, seems like some users might have issues with this test.
Disabling the test in docker would work now IMHO because Jenkins runs
pre-commit job on host machine, so it wouldn't get unnoticed if something
brakes.
Considering all this I would go with disabling the test on Docker env. But this
may worth a question on dev list.
> C client test failure on docker
> -------------------------------
>
> Key: ZOOKEEPER-4049
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4049
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.8
> Reporter: Norbert Kalmár
> Priority: Major
>
> A c test is constantly failing on docker environment:
> {code}
> [exec]
> /Downloads/zk359/apache-zookeeper-3.5.9/zookeeper-client/zookeeper-client-c/tests/TestClient.cc:789:
> Assertion: equality assertion failed [Expected: 0, Actual : -4]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
