[CALCITE-687] Make RemoteDriverTest thread-safe

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: avatica
• Assignee: Josh Elser
• Reporter: Julian Hyde
• Created: 17/Apr/15 18:06
• Updated: 27/Feb/24 22:24
• Resolved: 13/Sep/15 04:36

Description

There is apparently a thread safety issue in RemoteDriverTest.testStatementLifecycle. Here is output from <a href="https://travis-ci.org/julianhyde/incubator-calcite/jobs/58869949">Travis</a>:

ests run: 18, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 29.008 sec <<< FAILURE! - in org.apache.calcite.avatica.RemoteDriverTest
testStatementLifecycle(org.apache.calcite.avatica.RemoteDriverTest)  Time elapsed: 1.807 sec  <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<9>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:555)
	at org.junit.Assert.assertEquals(Assert.java:542)
	at org.apache.calcite.avatica.RemoteDriverTest.testStatementLifecycle(RemoteDriverTest.java:388)

Presumably this occurs in Travis because several tests are running concurrently.

I have disabled the test. We must fix this issue and re-enable the test.

Issue Links

• is related to: CALCITE-2250 Avatica with HSQLDB backend hangs when using multiple transactions
• is related to: CALCITE-874 ReflectiveRelMetadataProvider is not thread-safe
• links to: Pull request