[
https://issues.apache.org/jira/browse/HADOOP-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528469#comment-13528469
]
Aaron T. Myers commented on HADOOP-9112:
----------------------------------------
The output when a test times out is to have two lines right in a row which name
a test, without outputting any "Tests run:..." line in between. Given that, in
the past the way I've identified those tests which timed out or exited early is
by running this command on the output:
$ pcregrep -M '^Running org\.apache\.hadoop.*\n^[^(Tests run:)]' <file name>
Which will output any tests which were executed, but which surefire wasn't able
to determine which test cases that ran.
> 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: Improvement
> Reporter: Todd Lipcon
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
