Details

    • Type: Test
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      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.

        Attachments

        1. LUCENE-3429.patch
          8 kB
          Dawid Weiss
        2. LUCENE-3429.patch
          1 kB
          Robert Muir

          Issue Links

            Activity

              People

              • Assignee:
                dweiss Dawid Weiss
                Reporter:
                rcmuir Robert Muir
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: