[
https://issues.apache.org/jira/browse/HDFS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635450#comment-13635450
]
Hadoop QA commented on HDFS-4699:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12579356/HDFS-4699.1.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:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4274//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4274//console
This message is automatically generated.
> TestPipelinesFailover#testPipelineRecoveryStress fails sporadically
> -------------------------------------------------------------------
>
> Key: HDFS-4699
> URL: https://issues.apache.org/jira/browse/HDFS-4699
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha, 1.3.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-4699.1.patch, HDFS-4699.branch-0.23.1.patch,
> HDFS-4699.branch-1.1.patch
>
>
> I have seen {{TestPipelinesFailover#testPipelineRecoveryStress}} fail
> sporadically due to timeout during {{loopRecoverLease}}, which waits for up
> to 30 seconds before timing out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
