You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2020/03/13 03:07:00 UTC
[jira] [Updated] (CASSANDRA-15639) Jenkins build for jvm test
should use testclasslist to support parameterized tests
[ https://issues.apache.org/jira/browse/CASSANDRA-15639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-15639:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990)
Complexity: Low Hanging Fruit
Component/s: Build
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Jenkins build for jvm test should use testclasslist to support parameterized tests
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-15639
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15639
> Project: Cassandra
> Issue Type: Bug
> Components: Build
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
>
> We switched Circle CI to use testclasslist in CASSANDRA-15508 this was to solve the following exception
> {code}
> 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)
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org