Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2.0
-
None
Description
For debugging another issue, I've set the log level on travis to DEBUG.
After that, the Table API tests started failing
Failed tests: SetOperatorsITCase.testMinusAll:156 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusAll:156 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusAll:156 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusAll:156 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusDifferentFieldNames:204 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusDifferentFieldNames:204 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusDifferentFieldNames:204 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinusDifferentFieldNames:204 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinus:175 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinus:175 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinus:175 Internal error: Error occurred while applying rule DataSetScanRule SetOperatorsITCase.testMinus:175 Internal error: Error occurred while applying rule DataSetScanRule
Probably Calcite is executing additional assertions depending on the debug level.
Attachments
Issue Links
- links to