You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Berenguer Blasi (Jira)" <ji...@apache.org> on 2020/09/17 04:43:00 UTC
[jira] [Comment Edited] (CASSANDRA-15986) Repair tests flakiness
[ https://issues.apache.org/jira/browse/CASSANDRA-15986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197372#comment-17197372 ]
Berenguer Blasi edited comment on CASSANDRA-15986 at 9/17/20, 4:42 AM:
-----------------------------------------------------------------------
That's bc we lost history. I remember we had some Repair failure. I want to keep an eye longer I am not comfortable with this yet. Happy to take it back off your plate.
was (Author: bereng):
That's bc we lost history. I remember we had some Repair failure. I want to keep an eye longer.
> Repair tests flakiness
> ----------------------
>
> Key: CASSANDRA-15986
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15986
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
> Reporter: Berenguer Blasi
> Assignee: Ekaterina Dimitrova
> 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.
> _dtest-novnode.repair_tests.repair_test/TestRepair/test_simple_sequential_repair_
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org