You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/09/24 17:01:06 UTC

[jira] [Moved] (HADOOP-12439) test-patch should -1 for @Tests without a timeout

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

Allen Wittenauer moved YETUS-18 to HADOOP-12439:
------------------------------------------------

    Component/s:     (was: Test Patch)
            Key: HADOOP-12439  (was: YETUS-18)
        Project: Hadoop Common  (was: Yetus)

> test-patch should -1 for @Tests without a timeout
> -------------------------------------------------
>
>                 Key: HADOOP-12439
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12439
>             Project: Hadoop Common
>          Issue Type: New Feature
>            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)