[
https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562364#comment-17562364
]
Berenguer Blasi commented on CASSANDRA-17729:
---------------------------------------------
||Branch 1||Jenkins||Circle||
|[4.1 branch|http://example.com]|[CI
jenkins|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch/1822/]|[CI
circle|https://app.circleci.com/pipelines/github/bereng/cassandra/694/workflows/c08784ea-a9c8-49d5-abd9-0339f2338280]|
> Raise test timeouts
> -------------------
>
> Key: CASSANDRA-17729
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17729
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.1-beta
>
>
> We have seen for some time now junits timeout frequently on jenkins. This is
> probably down to it being a very loaded env. On circle we don't observe that
> behavior probably bc it's not so loaded.
> The question is whether it is time to raise timeouts as they might be hiding
> legit failures. As en experiment I raised timeouts in a branch and ran
> jenkins against it. What I see is that the last 4.1 run had 14 failures out
> of which 12 were timeouts. Increasing timeouts reveals what looks to be 9
> legit failures where 2 are timeouts that probably need to be investigated.
--
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
