Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sat, 27 Jun 2015 17:50:07 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12618675.1354587802000.35367.1435427407511@Atlassian.JIRA>
In-Reply-To: <JIRA.12618675.1354587802000@Atlassian.JIRA>
References: <JIRA.12618675.1354587802000@Atlassian.JIRA>
 <JIRA.12618675.1354587802574@arcas>
Subject: [jira] [Commented] (HADOOP-9112) test-patch should -1 for @Tests
 without a timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604280#comment-14604280 ] 

Allen Wittenauer commented on HADOOP-9112:
------------------------------------------

Moving this to be a subtask under yetus.  This is something we should build a plug-in for as part of the standard bits.

> test-patch should -1 for @Tests without a timeout
> -------------------------------------------------
>
>                 Key: HADOOP-9112
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9112
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Todd Lipcon
>         Attachments: HADOOP-9112-1.patch, HADOOP-9112-2.patch, HADOOP-9112-3.patch, HADOOP-9112-4.patch, HADOOP-9112-5.patch, HADOOP-9112-6.patch, HADOOP-9112-7.patch
>
>
> With our current test running infrastructure, if a test with no timeout set runs too long, it triggers a surefire-wide timeout, which for some reason doesn't show up as a failed test in the test-patch output. Given that, we should require that all tests have a timeout set, and have test-patch enforce this with a simple check


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)