Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
I have only seen this fail once, but haven't been looking hard.
http://cassci.datastax.com/view/trunk/job/trunk_testall/98/testReport/junit/org.apache.cassandra.tracing/TraceCompleteTest/testTraceComplete/
This is a weird one. It looks straightforward because the test is waiting for an event, but for only 250 milliseconds which is within the amount of time a node can just up and pause because life is hard.
However if you look at the test run it failed twice! Once in test and again in test-compression. Those odds aren't great.
I am tempted to increase the timeout and keep an eye open. It returns as soon as the event is available so it shouldn't have an impact on how long the test runs on average.
Attachments
Issue Links
- is superceded by
-
CASSANDRA-9429 Revert CASSANDRA-7807 (tracing completion client notifications)
-
- Resolved
-