[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129895#comment-15129895
]
Hudson commented on HDFS-9740:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9236 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9236/])
HDFS-9740. Use a reasonable limit in DFSTestUtil.waitForMetric() (vinayakumarb:
rev eb2fb943fd97c191fd7c4f5333087a28ee5c87d8)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/DFSTestUtil.java
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -----------------------------------------------------
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Kihwal Lee
> Assignee: Chang Li
> Fix For: 2.7.3
>
> Attachments: HDFS-9740-branch-2.7.patch, HDFS-9740-branch-2.patch,
> HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
