[ https://issues.apache.org/jira/browse/CASSANDRA-19683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852955#comment-17852955 ]
Brandon Williams commented on CASSANDRA-19683: ---------------------------------------------- bq. they were probably near the cusp of timing out before and are crossing it now. We can increase the timeouts for those tests to resolve that. They were already modifying [other timeouts|https://github.com/apache/cassandra-dtest/blob/trunk/cql_tracing_test.py#L29] so adding native_transport_timeout makes sense which I did [here|https://github.com/driftx/cassandra-dtest/commit/c2e56e4e116b489f925fda1f68893a91b8f91c17] and ran [CI w/repeats here|https://app.circleci.com/pipelines/github/driftx/cassandra/1653/workflows/654c04aa-7030-4d0f-b1bb-354378ab82dd/jobs/91646]. > Investigate dtest timeouts after CASSANDRA-19534 > ------------------------------------------------ > > Key: CASSANDRA-19683 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19683 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python > Reporter: Brandon Williams > Assignee: Brandon Williams > Priority: Normal > Fix For: 5.0-rc > > > We have seen increased dtest timeouts that don't appear to be environmental: > https://app.circleci.com/pipelines/github/driftx/cassandra/1651/workflows/738d1c92-0ffe-45e7-8ad4-f2646170ba76 > https://ci-cassandra.apache.org/job/Cassandra-5.0/238/ > I have confirmed these don't occur before CASSANDRA-19534 -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org