[
https://issues.apache.org/jira/browse/CASSANDRA-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559870#comment-14559870
]
Ariel Weisberg edited comment on CASSANDRA-9485 at 5/26/15 9:09 PM:
--------------------------------------------------------------------
Stripped it down, parallelized it, and was able to generate a seed that broke
it quickly. Although 2 out of the three systems crunched for a while with no
luck. You do have to modify the test to use a supplied random to
addAllRandomTest so that you can use the seed. There are issues with test
execution order that make sharing a random instance across multiple tests
sketchy.
The seed I got was 6540729295339161742.
was (Author: aweisberg):
Stripped it down, parallelized it, and was able to generate a seed that broke
it quickly. Although 2 out of the three systems crunched for a while with no
luck. You do have to modify the test to use a supplied random to
addAllRandomTest so that you can use the seed. There are issues with test
execution order that make sharing a random instance across multiple tests
sketchy.
The seed I got was 6540729295339161742 however when I hard coded it back in I
couldn't reproduce the problem. This makes me suspect there is an issue with
hashcode/equality or comparison.
> RangeTombstoneListTest.addAllRandomTest failed on trunk
> -------------------------------------------------------
>
> Key: CASSANDRA-9485
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9485
> Project: Cassandra
> Issue Type: Test
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
>
> http://cassci.datastax.com/job/trunk_utest/201/testReport/org.apache.cassandra.db/RangeTombstoneListTest/addAllRandomTest/
> The test is also broken for reproducibility. It doesn't print the seed used
> for the RNG so it isn't possible to take a failing run and reproduce it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
