[LUCENE-3429] improve build system when tests hang

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0-ALPHA
• Lucene Fields: New
• Assignee: Dawid Weiss
• Reporter: Robert Muir
• Created: 11/Sep/11 16:45
• Updated: 28/Aug/22 12:57
• Resolved: 16/Apr/12 12:11

Description

Currently, if tests hang in hudson it can go hung for days until we manually kill it.

The problem is that when a hang happens its probably serious, what we want to do (I think), is:

1. time out the build.
2. ensure we have enough debugging information to hopefully fix any hang.

So I think the ideal solution would be:

1. add a sysprop "-D" that LuceneTestCase respects, it could default to no timeout at all (some value like zero).
2. when a timeout is set, LuceneTestCase spawns an additional timer thread for the test class? method?
3. if the timeout is exceeded, LuceneTestCase dumps all thread/stack information, random seed information to hopefully reproduce the hang, and fails the test.
4. nightly builds would pass some reasonable -D for each test.

separately, I think we should have an "ant-level" timeout for the whole build, in case it goes completely crazy (e.g. jvm completely hangs or something else), just as an additional safety.

Issue Links

• is part of: LUCENE-3808 Switch LuceneTestCaseRunner to RandomizedRunner. Enforce Random sharing contracts. Enforce thread leaks.
• is related to: LUCENE-3489 Refactor test classes that use assumeFalse(codec != SimpleText, Memory) to use new annotation and move the expensive methods to separate classes

Sub-Tasks

• Detect the test thread by reference, not by name.: Closed