[
https://issues.apache.org/jira/browse/HDFS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794638#comment-13794638
]
Hadoop QA commented on HDFS-5278:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12608351/HDFS-5278.001.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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5184//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5184//console
This message is automatically generated.
> Reduce memory consumptions of TestDFSClientRetries
> --------------------------------------------------
>
> Key: HDFS-5278
> URL: https://issues.apache.org/jira/browse/HDFS-5278
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Priority: Minor
> Attachments: HDFS-5278.000.patch, HDFS-5278.001.patch
>
>
> TestDFSClientRetries::testDFSClientRetriesOnBusyBlocks() spawns about 50
> threads during the execution, each of which takes more than 6m memory. It
> makes debugging it in eclipse under the default settings difficult since it
> triggers the OutOfMemoryException.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
