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

Hudson commented on HDFS-9523:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-9523. libhdfs++: failure to connect to ipv6 host causes CI unit 
(james.clampffer: rev e18db92398adb456b8c15d2290b355417e39738c)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/fs/filesystem.cc
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/rpc_connection.h
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/rpc_engine.cc
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/rpc_engine.h
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/tests/rpc_engine_test.cc


> libhdfs++: failure to connect to ipv6 host causes CI unit tests to fail
> -----------------------------------------------------------------------
>
>                 Key: HDFS-9523
>                 URL: https://issues.apache.org/jira/browse/HDFS-9523
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Bob Hansen
>            Assignee: Bob Hansen
>            Priority: Major
>         Attachments: HDFS-9523.HDFS-8707.000.patch, 
> HDFS-9523.HDFS-8707.001.patch, HDFS-9523.HDFS-8707.002.patch, 
> HDFS-9523.HDFS-8707.test1.patch, failed_docker_run.txt
>
>
> When run under Docker, libhdfs++ is not connecting to the mini DFS cluster.   
> This is the reason the CI tests have been failing in the 
> libhdfs_threaded_hdfspp_test_shim_static test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to