[
https://issues.apache.org/jira/browse/HDFS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784675#comment-13784675
]
Hadoop QA commented on HDFS-5289:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12606455/HDFS-5289.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/5087//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5087//console
This message is automatically generated.
> Race condition in TestRetryCacheWithHA#testCreateSymlink causes spurious test
> failure
> -------------------------------------------------------------------------------------
>
> Key: HDFS-5289
> URL: https://issues.apache.org/jira/browse/HDFS-5289
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.1.1-beta
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-5289.patch
>
>
> The code to check if the operation has been completed on the active NN can
> potentially execute before the thread actually doing the operation has run.
> In this case the checking code will retry the check if the result of the
> check is null. However, the test operation does not in fact return null,
> instead throwing an exception if the file doesn't exist yet. We need to catch
> the exception and retry.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
