[ 
https://issues.apache.org/jira/browse/CASSANDRA-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352281#comment-17352281
 ] 

Berenguer Blasi commented on CASSANDRA-16670:
---------------------------------------------

CI is green already, please find links in the PR. Back of the envelope 
calculation is how splits were generated already. But there is big divergence 
between local, jenkins  devbranch and jenkins commit CI runs. So I don't think 
we can go much further i.e.. timeout is around 10m and there are 3 to 4 splits 
which should be under the new 4m timeout...

> Flaky ViewComplexTest and InsertUpdateIfConditionTest
> -----------------------------------------------------
>
>                 Key: CASSANDRA-16670
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16670
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0-rc2, 4.0, 4.x
>
>
> *ViewComplexTest*
> Flaky 
> [test|https://ci-cassandra.apache.org/job/Cassandra-4.0/43/testReport/junit/org.apache.cassandra.cql3/ViewComplexTest/testPartialDeleteSelectedColumnWithoutFlush_3_/]
> *InsertUpdateIfConditionTest* (CASSANDRA-16676)
> Fails 
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testListItem_2__clusterMinVersion_4_0_0_rc2_SNAPSHOT_/]
>  with a timeout. We can see in the history it takes quite a while in 
> [CI|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/history/]
>  _but_ it takes just 1m locally. Probably due to constrained resources. 
> Looking at the 
> [individual|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/]
>  test cases, for compression i.e., we can see 378 at an average of 1s each it 
> can easily go over the timeout of 240s. Recommendation is to either move to 
> 'long' section of to raise the timeout for the class for CI.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to