You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/09/07 11:46:22 UTC
[jira] [Created] (FLINK-4590) Some Table API tests are failing when
debug lvl is set to DEBUG
Robert Metzger created FLINK-4590:
-------------------------------------
Summary: Some Table API tests are failing when debug lvl is set to DEBUG
Key: FLINK-4590
URL: https://issues.apache.org/jira/browse/FLINK-4590
Project: Flink
Issue Type: Bug
Components: Table API & SQL
Affects Versions: 1.2.0
Reporter: Robert Metzger
For debugging another issue, I've set the log level on travis to DEBUG.
After that, the Table API tests started failing
{code}
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
{code}
Probably Calcite is executing additional assertions depending on the debug level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)