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

Hadoop QA commented on HDFS-6579:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12652012/HDFS-6579.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}.  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 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-HDFS-Build/7213//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7213//console

This message is automatically generated.

> TestSocketIOWithTimeout#testSocketIOWithTimeout fails on Power PC 
> ------------------------------------------------------------------
>
>                 Key: HDFS-6579
>                 URL: https://issues.apache.org/jira/browse/HDFS-6579
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.1.0-beta, 2.0.4-alpha, 2.2.0, 2.3.0, 2.4.0
>            Reporter: Jinghui Wang
>            Assignee: Jinghui Wang
>         Attachments: HDFS-6579.patch
>
>
> SocketOutputStream closes its writer if it's partial written. But on PPC, 
> after writing for some time, buf.capacity still equals buf.remaining. The 
> reason might be what's written on PPC is buffered,so the buf.remaining will 
> not change till a flush.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to