Hi,

There are frequently flakey test on Linux(JDK 11) related with TIMESTAMP(0) vs 
TIMESTAMP.

Below is failure test from [1].
FAILURE 0.0sec, org.apache.calcite.test.SqlToRelConverterExtendedTest > 
testTableValuedFunctionTumbleWithSubQueryParam()
1663 org.opentest4j.AssertionFailedError: plan ==> expected: < 
1664 LogicalProject(ORDERID=[$0], ROWTIME=[$1], window_start=[$2], 
window_end=[$3]) 
1665 LogicalTableFunctionScan(invocation=[TUMBLE($1, DESCRIPTOR($1), 
60000:INTERVAL MINUTE)], rowType=[RecordType(INTEGER ORDERID, TIMESTAMP(0) 
ROWTIME, TIMESTAMP(0) window_start, TIMESTAMP(0) window_end)]) 
1666 LogicalProject(ORDERID=[$0], ROWTIME=[$1]) 
1667 LogicalTableScan(table=[[CATALOG, SALES, SHIPMENTS]]) 
1668 > but was: < 
1669 LogicalProject(ORDERID=[$0], ROWTIME=[$1], window_start=[$2], 
window_end=[$3]) 
1670 LogicalTableFunctionScan(invocation=[TUMBLE($1, DESCRIPTOR($1), 
60000:INTERVAL MINUTE)], rowType=[RecordType(INTEGER ORDERID, TIMESTAMP 
ROWTIME, TIMESTAMP window_start, TIMESTAMP window_end)]) 
1671 LogicalProject(ORDERID=[$0], ROWTIME=[$1]) 
1672 LogicalTableScan(table=[[CATALOG, SALES, SHIPMENTS]]) 
1673 >

Below is failure test from [2]:
testPrintLimits
The only diff is TIMESTAMP(0) vs TIMESTAMP

Any clue?

[1] https://github.com/apache/calcite/runs/576436249
[2] https://github.com/apache/calcite/runs/584340845


- Haisheng

Reply via email to