Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-2523

PartiallyOrderedSetTest#testPosetBitsLarge takes ~80 seconds at Travis

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.17.0
    • Fix Version/s: 1.18.0
    • Component/s: core
    • Labels:
      None

      Description

      PartiallyOrderedSetTest#testPosetBitsLarge is quite large, and it performs exactly the same computation during test execution.

      I suggest to guard the test like testPosetBitsLarge2 with ENABLE_SLOW:

      Assume.assumeTrue("too slow to run every day", CalciteAssert.ENABLE_SLOW);

      Alternative options: reduce test complexity to make it faster, and/or randomize test execution so it explores new test cases on every execution. For instance, it could run for 5 seconds and explore new cases each time.

      Current test is more or less useless, and it does take noticeable CI time.

        Attachments

          Activity

            People

            • Assignee:
              julianhyde Julian Hyde
              Reporter:
              vladimirsitnikov Vladimir Sitnikov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: