Stefania commented on CASSANDRA-12784:

The failure was reproduced locally using the junit version specified in 
build.xml, which is 4.6, kind of old actually.

At least in 4.6, {{unit.framework.AssertionFailedError}} extends 
{{AssertionError}}. Let me add some debug information and see if I can 
reproduce it again tomorrow, I'll try to multiplex it on Jenkins and then we 
should know for sure what is going on.

Noted about changing the assert import. 

One more thing, if we want to leave {{testNewClusterWithMurmur3Partitioner}} at 
64 vnodes, then I suggest lowering the number of iterations in the flaky 
utility, or else a flaky run will time out.

> ReplicationAwareTokenAllocatorTest times out almost every time for 3.X and 
> trunk
> --------------------------------------------------------------------------------
>                 Key: CASSANDRA-12784
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12784
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.x
>         Attachments: ReplicationAwareTokenAllocatorTest.jfr.gz
> Example failure: 
> http://cassci.datastax.com/view/cassandra-3.X/job/cassandra-3.X_testall/lastCompletedBuild/testReport/org.apache.cassandra.dht.tokenallocator/ReplicationAwareTokenAllocatorTest/testNewClusterWithMurmur3Partitioner/

This message was sent by Atlassian JIRA

Reply via email to