[ https://issues.apache.org/jira/browse/CASSANDRA-15639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-15639: ------------------------------------------- Status: Open (was: Resolved) This broke all the jenkins jobs, as the test results are no longer available under {{build/test/output/TEST-*.xml}} > 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 > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 2h 40m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org