[CASSANDRA-15639] Jenkins build for jvm test should use testclasslist to support parameterized tests

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

Source Control Link

https://github.com/apache/cassandra-builds/commit/9781ca1b4e7489afa09a33b8943d599b47cfe233

Test and Documentation Plan

tested bash command locally against trunk. did not test Jenkins.

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Michael Semb Wever

• Created: 13/Mar/20 03:05
• Updated: 15/May/20 08:54
• Resolved: 15/Mar/20 22:37

Description

We switched Circle CI to use testclasslist in CASSANDRA-15508 this was to solve the following exception

ava.lang.Exception: No tests found matching Method testFailingMessage(org.apache.cassandra.distributed.test.FailingRepairTest) from org.junit.internal.requests.ClassRequest@551aa95a
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

The core issue is that the test locating logic in org.apache.cassandra.distributed.test.TestLocator does not handle parameterized tests so fails to find any tests for those classes.

I think it is better to switch to testclasslist as it helps make way for running tests concurrently.

Issue Links

• is broken by: CASSANDRA-15508 Failing jvm dtest: FailingRepairTest.testFailingMessage
• is related to: CASSANDRA-15651 Jenkins tests to use testclasslist where possible (like CircleCI)
• links to: GitHub Pull Request #14
• links to: GitHub Pull Request #471
• links to: GitHub Pull Request #472