[ 
https://issues.apache.org/jira/browse/CASSANDRA-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496635#comment-16496635
 ] 

Marcus Eriksson commented on CASSANDRA-14238:
---------------------------------------------

this only fails on 2.2, and most often because the DeletionTime is initialized 
with a negative local deletion time due to the randomness when corrupting the 
files. Can't reproduce on 3.0+

patch https://github.com/krummas/cassandra/commits/marcuse/14238 which hard 
codes the random seed to something I've tested works (ran the test in a loop 
for 10+ minutes)
test run on circle: 
https://circleci.com/gh/krummas/cassandra/tree/marcuse%2F14238

> Flaky Unittest: org.apache.cassandra.db.compaction.BlacklistingCompactionsTest
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14238
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14238
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Jay Zhuang
>            Assignee: Marcus Eriksson
>            Priority: Minor
>              Labels: testing
>             Fix For: 2.2.x
>
>
> The unittest is flaky
> {noformat}
>     [junit] Testcase: 
> testBlacklistingWithSizeTieredCompactionStrategy(org.apache.cassandra.db.compaction.BlacklistingCompactionsTest):
>  FAILED
>     [junit] expected:<8> but was:<25>
>     [junit] junit.framework.AssertionFailedError: expected:<8> but was:<25>
>     [junit]     at 
> org.apache.cassandra.db.compaction.BlacklistingCompactionsTest.testBlacklisting(BlacklistingCompactionsTest.java:170)
>     [junit]     at 
> org.apache.cassandra.db.compaction.BlacklistingCompactionsTest.testBlacklistingWithSizeTieredCompactionStrategy(BlacklistingCompactionsTest.java:71)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to