[
https://issues.apache.org/jira/browse/CASSANDRA-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350725#comment-17350725
]
Ekaterina Dimitrova commented on CASSANDRA-16670:
-------------------------------------------------
Looks good, I left only a few small questions/suggestions.
{quote}we won't know if we're flying under the timeouts until we merge and we
get a few runs in jenkins.
{quote}
I think that if a back-of-the-envelope calculation is done, that should help.
What I mean - we can check the timings of the splits and the timeout for the
long tests. The tests were not exceeding with a lot the timeout. We check the
ratio between the splits and the whole long test and the timeout for testsome
target and that should give us a good idea where we are. Then CI run of course,
but that rough calculation should help to establish a good baseline I think.
Worst case scenario we can loop them now when we have the multiplexer :)
> 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: [email protected]
For additional commands, e-mail: [email protected]
