Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Cannot Reproduce
-
1.0.0
-
None
Description
Noticed the following error in one of the travis-ci test runs. If it makes sense, we should adjust the test timeout so that this does not fail as often.
In org.apache.storm.cassandra.DynamicStatementBuilderTest
java.lang.AssertionError: Cassandra daemon did not start within timeout
This is annoying because test for unrelated changes can fail, causing confusion.