[
https://issues.apache.org/jira/browse/HDFS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038135#comment-13038135
]
Matt Foley commented on HDFS-1852:
----------------------------------
Besides the three remaining open issues above, we also have three
infrequent-intermittent issues that may still exist. All were last seen in
build 594, so it possible they were addressed.
org.apache.hadoop.cli.TestHDFSCLI.testAll - v intermittent, last 566, 579, 587,
594
org.apache.hadoop.hdfs.server.datanode.TestBlockRecovery.testErrorReplicas - v
intermittent, last 559, 566, 579, 594
org.apache.hadoop.hdfs.server.datanode.TestBlockReplacement.testBlockReplacement
- v intermittent, last 565, 578, 594
Recording here for watchlist purposes.
> Umbrella task: Clean up HDFS unit test recurring failures
> ----------------------------------------------------------
>
> Key: HDFS-1852
> URL: https://issues.apache.org/jira/browse/HDFS-1852
> Project: Hadoop HDFS
> Issue Type: Test
> Components: test
> Affects Versions: 0.22.0
> Reporter: Matt Foley
>
> Recurring failures and false positives undermine CI by encouraging developers
> to ignore unit test failures. Let's clean these up!
> Some are intermittent due to timing-sensitive conditions. The unit tests for
> background thread activities (such as block replication and corrupt replica
> detection) often use "wait while" or "wait until" loops to detect results.
> The quality and robustness of these loops vary widely, and common usages
> should be moved to DFSTestUtil.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
