Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0, 6.0
    • Component/s: general/test
    • Labels:
      None
    • Environment:
    • Lucene Fields:
      New, Patch Available

      Description

      The tests labelled @Monster are having a very hard time passing. Initially, there were some real failures on tests that push the 2 billion envelope, as well as some test bugs regarding suite timeouts and the quantity of date sent to sysout. Michael McCandless committed a fix for the real failures and the initial sysout problems.

      Trying to move @SuppressSysoutChecks to the definition of @Monster didn't work. I'm also having trouble defining the suite timeouts. One test that says it takes about 45 minutes hit the six hour timeout that I had configured for the suite, and failed.

      What sort of machine should we use as a "normal" machine for deciding on suite timeouts? My machine is over four years old, but it's got three 2.5Ghz cores and 12GB of RAM. That's certainly not a completely modern machine, but it's not exactly slow.

        Attachments

        1. LUCENE-6002.patch
          12 kB
          Shawn Heisey
        2. LUCENE-6002.patch
          13 kB
          Shawn Heisey
        3. LUCENE-6002.patch
          13 kB
          Shawn Heisey
        4. LUCENE-6002.patch
          7 kB
          Shawn Heisey
        5. LUCENE-6002.patch
          7 kB
          Shawn Heisey

          Issue Links

            Activity

              People

              • Assignee:
                elyograg Shawn Heisey
                Reporter:
                elyograg Shawn Heisey
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: