[
https://issues.apache.org/jira/browse/CASSANDRA-15986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181908#comment-17181908
]
Ekaterina Dimitrova edited comment on CASSANDRA-15986 at 8/21/20, 2:13 PM:
---------------------------------------------------------------------------
I am puzzled what is going on, rebased yesterday and started the tests on the
same VM I was using before - there is no single failure! I left it looping
overnight... (without the suggested patch to make the issue more obvious). I
don't see any related patch committed recently?
At the same time, I still see it failing in Jenkins and CircleCI these days
with the same error.
I would suggest to commit the suggested patch and continue monitoring, not
close the ticket in the next 2 weeks for example.WDYT [~maedhroz], [~Bereng]?
I wish there was a way to multiplex a test In Jenkins. I will ping Mick to
check how hard this would be to be implemented. It will help a lot in such
cases.
I can try to go through the logs further without being able to reproduce the
failure but not sure how reasonable it will be to spend that time now. As I
said in the beginning, the suggestion of [~Bereng] sounds reasonable to try to
stabilize them, I might be wrong, looking for a second opinion. :-)
was (Author: e.dimitrova):
I am puzzled what is going on, rebased yesterday and started the tests on the
same VM I was using before - there is no single failure! I left it looping
overnight... (without the suggested patch to make the issue more obvious). I
don't see any related patch committed recently?
At the same time, I still see it failing in Jenkins and CircleCI these days
with the same error.
I would suggest to commit the suggested patch and continue monitoring, not
close the ticket in the next 2 weeks for example.WDYT [~maedhroz], [~Bereng]?
I wish there was a way to multiplex a test In Jenkins. I will ping Mick to
check how hard this would be to be implemented. It will help a lot in such
cases, looking for a second opinion. :-)
I can try to go through the logs further without being able to reproduce the
failure but not sure how reasonable it will be to spend that time now. As I
said in the beginning, the suggestion of [~Bereng] sounds reasonable to try to
stabilize them, I might be wrong.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
