hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1852) Umbrella task: Clean up HDFS unit test recurring failures
Date Tue, 03 May 2011 21:59:03 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matt Foley updated HDFS-1852:
-----------------------------

    Description: 
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.

  was:Both namenode and datanode have multiple background threads responsible for detecting
and responding to time-changing conditions, such as corrupt replicas, under- or over-replicated
blocks, etc.  The unit tests that attempt to exercise these threads often duplicate complex
combinations of actions, and use "wait for" or "wait until" loops to detect the results. 
The quality and robustness of these loops vary widely, and some problematic ones cause recurring
intermittent false positives in Hudson.  This is an umbrella task for a set of bugs to be
opened, to clean up these usages and move the common ones to DFSTestUtil.

        Summary: Umbrella task: Clean up HDFS unit test recurring failures   (was: Umbrella
task: Clean up HDFS unit tests for timing-sensitive conditions, improve both condition stimulators
and condition detection loops)

> 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

Mime
View raw message