You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Vladimir Sitnikov (JIRA)" <ji...@apache.org> on 2018/09/01 01:10:00 UTC

[jira] [Created] (CALCITE-2523) PartiallyOrderedSetTest#testPosetBitsLarge takes ~80 seconds at Travis

Vladimir Sitnikov created CALCITE-2523:
------------------------------------------

             Summary: PartiallyOrderedSetTest#testPosetBitsLarge takes ~80 seconds at Travis
                 Key: CALCITE-2523
                 URL: https://issues.apache.org/jira/browse/CALCITE-2523
             Project: Calcite
          Issue Type: Bug
          Components: core
    Affects Versions: 1.17.0
            Reporter: Vladimir Sitnikov
            Assignee: Julian Hyde


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:

{code:java}Assume.assumeTrue("too slow to run every day", CalciteAssert.ENABLE_SLOW);{code}

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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)