[
https://issues.apache.org/jira/browse/HADOOP-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585992#comment-13585992
]
Alejandro Abdelnur edited comment on HADOOP-9330 at 2/25/13 5:06 PM:
---------------------------------------------------------------------
Cos, {{@Test{timeout=<>)}} exist, yes, if we can tweak that timeout to take a
global ratio into account then we are good.
Agree with Steve that subclassing should be a convenience, not a requirement.
If you subclass you get the @Rule setting for free, otherwise you have to do it
yourself.
was (Author: tucu00):
Cos, @Test{timeout=<>) exist, yes, if we can tweak that timeout to take a
global ratio into account then we are good.
Agree with Steve that subclassing should be a convenience, not a requirement.
If you subclass you get the @Rule setting for free, otherwise you have to do it
yourself.
> Add custom JUnit4 test runner with configurable timeout
> -------------------------------------------------------
>
> Key: HADOOP-9330
> URL: https://issues.apache.org/jira/browse/HADOOP-9330
> Project: Hadoop Common
> Issue Type: Test
> Components: test
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
>
> HADOOP-9112 has added a requirement for all new test methods to declare a
> timeout, so that jenkins/maven builds will have better information on a
> timeout.
> Hard coding timeouts into tests is dangerous as it will generate spurious
> failures on slower machines/networks and when debugging a test.
> I propose providing a custom JUnit4 test runner that test cases can declare
> as their test runner; this can provide timeouts specified at run-time, rather
> than in-source.
--
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
