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

Hadoop QA commented on HDFS-2630:
---------------------------------

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

This message is automatically generated.

> Chance for Stream leakage in CompressorStream
> ---------------------------------------------
>
>                 Key: HDFS-2630
>                 URL: https://issues.apache.org/jira/browse/HDFS-2630
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: SreeHari
>            Assignee: Rushabh S Shah
>            Priority: Minor
>             Fix For: 0.23.0
>
>         Attachments: HDFS-2630.patch
>
>
> In CompressorStream.close , finish() can throw IOException . But out will not 
> be closed in that situation since it is not in finally 



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

Reply via email to