[
https://issues.apache.org/jira/browse/HDFS-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828625#comment-13828625
]
Hadoop QA commented on HDFS-5543:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12615067/HDFS-5543.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:red}-1 javadoc{color}. The javadoc tool appears to have generated
-14 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/5520//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5520//console
This message is automatically generated.
> fix narrow race condition in TestPathBasedCacheRequests
> -------------------------------------------------------
>
> Key: HDFS-5543
> URL: https://issues.apache.org/jira/browse/HDFS-5543
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: test
> Affects Versions: 3.0.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-5543.001.patch
>
>
> TestPathBasedCacheRequests has a narrow race condition in
> testWaitForCachedReplicasInDirectory where an assert checking the number of
> bytes cached may fail. The reason is because waitForCachedBlock looks at the
> NameNode data structures directly to see how many replicas are cached, but
> the scanner asynchronously updates the cache entries with this information.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
