[CASSANDRA-17729] Raise test timeouts

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-beta1, 5.0-alpha1, 5.0
• Component/s: Test/unit
• Bug Category: Degradation
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test
• Platform: All
• Since Version: 4.1-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/14fc06a3ce007b0cbf3bc88c3d8c247da65fc036

Test and Documentation Plan

In the ticket

• Assignee: Berenguer Blasi
• Reporter: Berenguer Blasi

Authors

Berenguer Blasi

Reviewers

Berenguer Blasi, Michael Semb Wever

• Created: 05/Jul/22 04:34
• Updated: 12/Sep/23 13:02
• Resolved: 14/Jul/22 09:45

Description

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.