Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-3139

LuceneTestCase.afterClass does not print enough information if a temp-test-dir fails to delete

    Details

    • Type: Test
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2, 4.0-ALPHA
    • Component/s: general/test
    • Labels:
      None
    • Lucene Fields:
      New, Patch Available

      Description

      I've hit an exception from LTC.afterClass when _TestUtil.rmDir failed (on write.lock, as if some test did not release resources). However, I had no idea which test caused that (i.e. opened the temp directory and did not release resources).

      I think we should do the following:

      • Track in LTC a map from dirName -> StackTraceElement
      • In afterClass if _TestUtil.rmDir fails, print the STE of that particular dir, so we know where was this directory created from
      • Make tempDirs private and create accessor method, so that we control the inserts to this map (today the Set is updated by LTC, _TestUtils and TestBackwards !)

        Attachments

        1. LUCENE-3139.patch
          15 kB
          Shai Erera
        2. LUCENE-3139.patch
          8 kB
          Shai Erera
        3. LUCENE-3139.patch
          4 kB
          Shai Erera

          Activity

            People

            • Assignee:
              shaie Shai Erera
              Reporter:
              shaie Shai Erera
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: