Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <14077497.184141290121634879.JavaMail.jira@thor>
Date: Thu, 18 Nov 2010 18:07:14 -0500 (EST)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-7043) Regressions (tests failing after a
 patch application) should be automatically detected and marked as such
In-Reply-To: <33486288.183471290120435077.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik updated HADOOP-7043:
---------------------------------------

    Summary: Regressions (tests failing after a patch application) should be automatically detected and marked as such  (was: Regressions (tests failing after a patch applicarion) should be automatically detected and marked as such)

Right. Nigel and I had this conversation earlier in the day and that was _exactly_ his idea of the test-patch modification.

> Regressions (tests failing after a patch application) should be automatically detected and marked as such
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7043
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7043
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Boudnik
>
> The idea is pretty simple: whenever a test failure happens test-patch (or Hudson though the meaning of a plugin) needs to check appropriate project JIRAs to see if the test name is mentioned in one of the 'well-known' fields. Perhaps Description or Title are the best candidates for this role.
> The benefits are apparent: 
> - saving time on analysis of intermittent failures (Hudson is only able to calculate failure age for a consequent failures i.e. where there's no "gaps" between failure episodes)
> - semi-intelligent check for possible regressions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.