[CASSANDRA-15649] test.distributed.timeout no longer respected in CircleCI

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.17, 3.0.21, 3.11.7, 4.0-alpha4, 4.0
• Component/s: Build, CI
• Labels: CI pull-request-available
• Bug Category: Degradation - Performance Bug/Regression
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• Since Version: 2.2.16

Source Control Link

https://github.com/apache/cassandra/commit/b49084733792d9a24b205008ed4da870acf0b670

Test and Documentation Plan

since this only impacts CircleCI, unit and jvm-dtests are the only tests run

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Michael Semb Wever

• Created: 20/Mar/20 20:51
• Updated: 15/May/20 08:53
• Resolved: 27/Mar/20 11:31

Description

After switching jvm dtest over testclasslist (CASSANDRA-15508) we no longer respect the dtest timeout and instead use the unit test timeout (4m vs 6m).

This does not impact Jenkins as I made sure to check that before calling testclasslist; though this does impact 2.2, 3.0, and 3.11 as well.

Config	Trunk	3.11	3.0	2.2
LOWER	Circle CI	Circle CI	Circle CI	Circle CI
HIGHER	Circle CI	TBD	TBD	TBD

CI Failures were flaky tests, below are their links

• CASSANDRA-15630

Issue Links

• relates to: CASSANDRA-15630 Fix flakey testSerializeError - org.apache.cassandra.net.ConnectionTest
• links to: GitHub Pull Request #479
• links to: GitHub Pull Request #483
• links to: GitHub Pull Request #484
• links to: GitHub Pull Request #485