[
https://issues.apache.org/jira/browse/HDFS-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963798#comment-13963798
]
Hadoop QA commented on HDFS-6209:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12639319/HDFS-6209.01.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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestSafeMode
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6626//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6626//console
This message is automatically generated.
> Fix flaky test
> TestValidateConfigurationSettings.testThatDifferentRPCandHttpPortsAreOK
> --------------------------------------------------------------------------------------
>
> Key: HDFS-6209
> URL: https://issues.apache.org/jira/browse/HDFS-6209
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.4.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HDFS-6209.01.patch
>
>
> The test depends on hard-coded port numbers being available. It should retry
> if the chosen port is in use.
> Exception details below in a comment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
