It’s a tough call. It is probable that the problem existed already and the change merely surfaced it.
> On May 28, 2019, at 5:17 PM, Stamatis Zampetakis <[email protected]> wrote: > > It is not the only test that is failing after commit [1] but all the new > tests that were added. > > I've seen the problem on Jenkins on all JDKS but I cannot reproduce it > locally. > I guess we have to do with a race condition most likely due to the > concurrent execution of tests with surefire. > > Should we revert the commit till we find a solution? > > [1] > https://github.com/apache/calcite/commit/82e7d4e760cb203d31956c55e38e0fdd56119d58 > > On Tue, May 28, 2019 at 7:57 PM Julian Hyde <[email protected]> wrote: > >> I have seen this intermittent failure 3 times in the last week: >> >> [INFO] Running org.apache.calcite.plan.RelOptUtilTest >> [ERROR] Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: >> 0.411 s <<< FAILURE! - in org.apache.calcite.plan.RelOptUtilTest >> [ERROR] >> testPushDownJoinConditionsWithExpandedIsNotDistinctUsingCase(org.apache.calcite.plan.RelOptUtilTest) >> Time elapsed: 0.349 s <<< ERROR! >> org.apache.calcite.rel.metadata.CyclicMetadataException >> at >> org.apache.calcite.plan.RelOptUtilTest.testPushDownJoinConditionsWithExpandedIsNotDistinctUsingCase(RelOptUtilTest.java:445) >> >> I have seen it on Oracle JDK 12 and OpenJDK 10. The test was only added on >> May 22 so I assume that it will continue to fail intermittently until we do >> something. >> >> Anyone have any ideas? >> >> Laurent, As you added the test can you please look into it? >> >> Julian >> >>
