[
https://issues.apache.org/jira/browse/HADOOP-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205302#comment-14205302
]
Hadoop QA commented on HADOOP-9576:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680636/HADOOP-9576-003.patch
against trunk revision eace218.
{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}. There were no new javadoc 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 2.0.3) 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/5057//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5057//console
This message is automatically generated.
> Make NetUtils.wrapException throw EOFException instead of wrapping it as
> IOException
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-9576
> URL: https://issues.apache.org/jira/browse/HADOOP-9576
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.6.0
> Reporter: Jian He
> Assignee: Steve Loughran
> Attachments: HADOOP-9576-003.patch
>
>
> In case of EOFException, NetUtils is now wrapping it as IOException, we may
> want to throw EOFException as it is, since EOFException can happen when
> connection is lost in the middle, the client may want to explicitly handle
> such exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
