From beb91446c7fe9a916b461560110798d0f47257fa Mon Sep 17 00:00:00 2001 From: Nikolay Martynov Date: Thu, 21 Jun 2018 12:00:26 -0400 Subject: [PATCH] Increase Cassandra embedded server start up timeout To try to make tests less prone to false positives. --- .../src/test/groovy/CassandraClientTest.groovy | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/dd-java-agent/instrumentation/datastax-cassandra-3.2/src/test/groovy/CassandraClientTest.groovy b/dd-java-agent/instrumentation/datastax-cassandra-3.2/src/test/groovy/CassandraClientTest.groovy index 1e5cd5e382..54a33fd29f 100644 --- a/dd-java-agent/instrumentation/datastax-cassandra-3.2/src/test/groovy/CassandraClientTest.groovy +++ b/dd-java-agent/instrumentation/datastax-cassandra-3.2/src/test/groovy/CassandraClientTest.groovy @@ -9,7 +9,13 @@ import org.cassandraunit.utils.EmbeddedCassandraServerHelper class CassandraClientTest extends AgentTestRunner { def setupSpec() { - EmbeddedCassandraServerHelper.startEmbeddedCassandra(40000L) + /* + This timeout seems excessive but we've seen tests fail with timeout of 40s. + TODO: if we continue to see failures we may want to consider using 'real' Cassandra + started in container like we do for memcached. Note: this will complicate things because + tests would have to assume they run under shared Cassandra and act accordingly. + */ + EmbeddedCassandraServerHelper.startEmbeddedCassandra(120000L) } def cleanupSpec() {