[
https://issues.apache.org/jira/browse/HDFS-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619164#comment-13619164
]
Hadoop QA commented on HDFS-4643:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576419/hdfs-4643.txt
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 3 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-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.fs.TestFcHdfsSymlink
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4173//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4173//console
This message is automatically generated.
> Fix flakiness in TestQuorumJournalManager
> -----------------------------------------
>
> Key: HDFS-4643
> URL: https://issues.apache.org/jira/browse/HDFS-4643
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: qjm, test
> Affects Versions: 3.0.0, 2.0.3-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Attachments: hdfs-4643.txt, hdfs-4643.txt, hdfs-4643.txt
>
>
> TestQuorumJournalManager can occasionally fail if two consecutive test cases
> pick the same port number for the JournalNodes. In this case, sometimes an
> IPC client can be cached from a previous test case, and then fail when it
> tries to make an IPC over that cached connection to the now-broken
> connection. We need to more carefully call close() on all the QJMs to prevent
> this.
--
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
