[
https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566707#comment-17566707
]
Berenguer Blasi commented on CASSANDRA-17729:
---------------------------------------------
||PR||CI||
|Trunk https://github.com/apache/cassandra/pull/1730|Ci
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/718/workflows/3f3a4b86-3110-4a95-be1b-5c2eb92cc507]
CI
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/718/workflows/128a413f-59d5-4b00-acc1-c3a11a453433]|
|Trunk https://github.com/apache/cassandra/pull/1731|CI
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/719/workflows/8408ab3a-333c-4c10-bd67-34542ee2984a]
CI
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/719/workflows/66ba9760-cb63-4596-8e48-47d65e39f639]|
> 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, 4.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
