[
https://issues.apache.org/jira/browse/CASSANDRA-16952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432696#comment-17432696
]
Ekaterina Dimitrova commented on CASSANDRA-16952:
-------------------------------------------------
Hey [~k-rus], sorry, I wasn't clear. I think we spent so much time on tests
fixing that we started to understand each other with two words and just handle
quickly certain tickets/issues without giving enough context to others.
Something we need to do better.
{{test_multiple_repair}} of
{{repair_tests.incremental_repair_test.TestIncRepair is
[stable|https://jenkins-cm4.apache.org/job/Cassandra-trunk/791/testReport/dtest-large-novnode.repair_tests.incremental_repair_test/]
in Jenkins.}}
I [ran it 1000 times in Circle
CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1163/workflows/16b60bae-caa5-4ede-938b-6dd3fa7bb3c9/jobs/6809]
and it timed out 4 times.
{{test_simultaneous_bootstrap is also stable in Jenkins and here it is [1000
times completed
successfully|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1162/workflows/dfe5ad1e-b46c-415e-b91c-f2fc7ef617e1/jobs/6810]
in CircleCI.}}
It seems like the tests timed out in Circle which happens often with different
tests, it is related to the different resources, etc. It is very hard to make
everything passing everywhere on all infrastructure as time is always a thing.
If you reproduce different issue, let's open a ticket. Please let me know if
you have any questions or concerns.
[~brandon.williams], any objections around {{test_multiple_repair}}{{? I see
that log archives are already wiped from [~k-rus]'s runs but you can check the
logs from those I linked today. }}
> Number of dtest are flaky due to timeout
> ----------------------------------------
>
> Key: CASSANDRA-16952
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16952
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Ruslan Fomkin
> Priority: Normal
>
> {{test_multiple_repair}} of
> {{repair_tests.incremental_repair_test.TestIncRepair}} has failed on CircleCI
> build and was identified as flaky by CircleCI. See [the
> failure|https://app.circleci.com/pipelines/github/k-rus/cassandra/10/workflows/846bfcdc-b33e-4e57-9252-56ef445d115a/jobs/92/tests#failed-test-0]
> The error:
> {code:python}
> > raise self._final_exception
> E cassandra.OperationTimedOut: errors={<Host: 127.0.0.3:9042
> datacenter1>: ConnectionShutdown('Connection to 127.0.0.3:9042 was
> closed',)}, last_host=127.0.0.1:9042
> ../env3.6/src/cassandra-driver/cassandra/cluster.py:4894: OperationTimedOut
> {code}
> Similarly {{test_simultaneous_bootstrap}} from
> {{bootstrap_test.TestBootstrap}} failed in a CircleCI build and was
> identified as flaky by CircleCI. See for example [this
> build|https://app.circleci.com/pipelines/github/k-rus/cassandra/16/workflows/9987f757-93f3-4c57-af73-09f4b217ee49/jobs/161/tests#failed-test-0].
> The same timeout error as above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
