Re: [DISCUSS] reasonable duration for tests in the Calcite codebase
I'm inclined to do something with LatticeTest (== mark it as disabled or
something like that)
It fails too often, and the only thing it does it tests HSQL (or H2?)
ability to perform join queries. It has nothing to do with Calcite.
Current LatticeTests definitely harms Calcite development and it makes
"Calcite-Master - Build # 944 - Still Failing" messages virtually useless.