[
https://issues.apache.org/jira/browse/CASSANDRA-15894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152558#comment-17152558
]
Benjamin Lerer edited comment on CASSANDRA-15894 at 7/7/20, 8:15 AM:
---------------------------------------------------------------------
My guess is that some tests were border line in term of duration and that the
team in charge of the tests at that time discovered that if you run them twice
you reduce the number of failures (the dtest project had different owners over
time).
For that test I would simply try to see if we can increase reasonably the
timeout at the point of failure.
was (Author: blerer):
My guess is that some tests were border line in term of duration and that the
team in charge of the tests at that time discovered that if you run them twice
you reduce the number of failures (the dtest project had different owner over
time).
For that test I would simply try to see if we can increase reasonably the
timeout at the point of failure.
> JAVA 8: test_multiple_repair -
> repair_tests.incremental_repair_test.TestIncRepair
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-15894
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15894
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Ekaterina Dimitrova
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-rc
>
> Attachments: test_multiple_repair_log.txt
>
>
> JAVA 8: test_multiple_repair -
> repair_tests.incremental_repair_test.TestIncRepair
> Fails locally and in CircleCI:
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/222/workflows/46515d14-9be4-4edb-8db4-5930312d2bfb/jobs/1329
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
