[
https://issues.apache.org/jira/browse/CALCITE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Sitnikov resolved CALCITE-2523.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.18.0
Fixed in
https://git-wip-us.apache.org/repos/asf?p=calcite.git;a=commit;h=3df638c9d34cd83eeb381dd288be786e97ec4c39
> 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
> Priority: Major
> Fix For: 1.18.0
>
>
> 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)
