[
https://issues.apache.org/jira/browse/CASSANDRA-15986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177701#comment-17177701
]
Berenguer Blasi commented on CASSANDRA-15986:
---------------------------------------------
So I have tried with a VM on diff memory settings down to 3GB and even capping
CPU to 10% only. That thing is solid as a rock. I can't repro. On too low specs
it starts to fail on legit timeouts on other areas. So no way to repro this one
for me.
On the other hand I tried to repro the Tracing test failures and I did manage
to. So I will try that once I am back from my 1w break #justfyi
> Repair tests flakiness
> ----------------------
>
> Key: CASSANDRA-15986
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15986
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
> Reporter: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Repair tests come up in test failure reports every now and then. I have tried
> to repro the
> [latest|https://ci-cassandra.apache.org/job/Cassandra-trunk/241/testReport/junit/dtest-novnode.repair_tests.repair_test/TestRepair/test_simple_sequential_repair/]
> locally 100 times with no luck.
> Still from experience from fixing other flaky tests I have some intuition
> where the problems may lie. The proposed fix should add no harm if merged. We
> can reopen the ticket if repair tests keep failing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
