[
https://issues.apache.org/jira/browse/HDFS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756757#action_12756757
]
Tsz Wo (Nicholas), SZE commented on HDFS-540:
---------------------------------------------
Got a different failure case:
{noformat}
Testcase: testCorruptBlock took 2.684 sec
FAILED
expected:<1> but was:<0>
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at
org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics.testCorruptBlock(TestNameNodeMetrics.java:114)
{noformat}
The following is the one Gary mentioned earlier.
{noformat}
expected:<0> but was:<1>
junit.framework.AssertionFailedError: expected:<0> but was:<1>
at
org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics.testCorruptBlock(TestNameNodeMetrics.java:118)
{noformat}
> TestNameNodeMetrics fails intermittently
> ----------------------------------------
>
> Key: HDFS-540
> URL: https://issues.apache.org/jira/browse/HDFS-540
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.21.0
>
> Attachments: HDFS-540.patch, HDFS-540.patch
>
>
> TestNameNodeMetrics has strict timing constraint that relies on block
> management functionality and can fail intermittently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
