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

Improve test reproducibility of ConcurrentMergeScheduler

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      If things go wrong based on merges with concurrentmergescheduler in tests, its always more difficult to reproduce.

      But we make it worse, CMS can base its behavior on:

      • number of cpus.
      • whether drives are SSDs.

      We should just allow a (undocumented, for testing) sysprop backdoor to override both of these. This way, it can be set to values completely based on the random seed in LuceneTestCase init, and its not a reproducibility trap.

      Its true we try to set explicit values for LuceneTestCase.newIndexWriterConfig() and so forth. But not all tests use randomized IW configs.

        Attachments

        1. LUCENE-6437.patch
          4 kB
          Michael McCandless

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rcmuir Robert Muir
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: