[ 
https://issues.apache.org/jira/browse/CASSANDRA-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024205#comment-17024205
 ] 

Marcus Eriksson commented on CASSANDRA-15508:
---------------------------------------------

looks like the 3.11 in-jvm upgrade dtests fail with: 
{{java.lang.RuntimeException: No v22 versions found}}

also the 3.0 and 3.11 workflows don't have {{start_jvm_upgrade_dtest}} in the 
top level like trunk does?

> Failing jvm dtest: FailingRepairTest.testFailingMessage
> -------------------------------------------------------
>
>                 Key: CASSANDRA-15508
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15508
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Marcus Eriksson
>            Assignee: David Capwell
>            Priority: Normal
>              Labels: pull-request-available
>         Attachments: Screen Shot 2020-01-17 at 4.51.17 PM.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> It seems we can't run parameterized unit tests with {{ant testsome}}:
> {code}
> $ ant testsome 
> -Dtest.name=org.apache.cassandra.distributed.test.FailingRepairTest 
> -Dtest.methods=testFailingMessage
> ....
> [junit-timeout] Testcase: 
> initializationError(org.junit.runner.manipulation.Filter):    Caused an ERROR
> [junit-timeout] No tests found matching Method 
> testFailingMessage(org.apache.cassandra.distributed.test.FailingRepairTest) 
> from org.junit.internal.requests.ClassRequest@4d95d2a2
> [junit-timeout] java.lang.Exception: No tests found matching Method 
> testFailingMessage(org.apache.cassandra.distributed.test.FailingRepairTest) 
> from org.junit.internal.requests.ClassRequest@4d95d2a2
> [junit-timeout]         at 
> java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to