hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
Date Sat, 18 May 2013 00:53:16 GMT

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

Hadoop QA commented on HADOOP-9440:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12575838/HADOOP-9440.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/2548//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/2548//console

This message is automatically generated.
                
> Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
> ------------------------------------------------------------
>
>                 Key: HADOOP-9440
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9440
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.5-beta
>            Reporter: Tian Hong Wang
>              Labels: patch
>         Attachments: HADOOP-9440.patch
>
>
> TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0,
TestIPC.testIpcTimeout &  TestIPC.testIpcConnectTimeout will fail.
> java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException:
500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected
local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host
is: "louis-ThinkPad-T410/127.0.0.1"; destination host is: "louis-ThinkPad-T410":50353; 
> 	at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761)
> 	at org.apache.hadoop.ipc.Client.call(Client.java:1239)
> 	at org.apache.hadoop.ipc.Client.call(Client.java:1163)
> 	at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492)
> testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC)  Time elapsed: 2009 sec  <<<
ERROR!
> java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException:
2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected
local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host
is: "louis-ThinkPad-T410/127.0.0.1"; destination host is: "louis-ThinkPad-T410":39525; 
> 	at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761)
> 	at org.apache.hadoop.ipc.Client.call(Client.java:1239)
> 	at org.apache.hadoop.ipc.Client.call(Client.java:1163)
> 	at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515)
> TestIPC.testIpcTimeout &  TestIPC.testIpcConnectTimeout fails because it catches
the  com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message