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

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

Sean Busbey moved HADOOP-9112 to YETUS-18:
------------------------------------------

    Target Version/s:   (was: 3.0.0)
         Component/s:     (was: build)
                      Test Patch
                 Key: YETUS-18  (was: HADOOP-9112)
             Project: Yetus  (was: Hadoop Common)

> test-patch should -1 for @Tests without a timeout
> -------------------------------------------------
>
>                 Key: YETUS-18
>                 URL: https://issues.apache.org/jira/browse/YETUS-18
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>            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)