Details
-
New Feature
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-9389 test-patch marks -1 due to a context @Test by mistake
- Resolved
- is related to
-
HADOOP-9330 Add custom JUnit4 test runner with configurable timeout
- Resolved