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

Andres de la Peña commented on CASSANDRA-18722:
-----------------------------------------------

None of the above CircleCI runs contains the repeated runs of the modified 
files ({{JMXFeatureTest.java}}). I think this is due to a bug in the non-public 
script used to generate the CircleCI config file.

Those repeated runs can be generated with the project's 
[{{.circleci/generate.sh}}|https://github.com/apache/cassandra/blob/trunk/.circleci/generate.sh]
 script.

The absence of repeated runs can be easily detected by looking at the CI 
results, in the workflow view. If the patch contains any changes on tests there 
should be jobs named with the {{_repeat}} suffix. One can also check whether 
the pushed {{.circleci/config.yml}} file contains the names of relevant tests.

> Support Dynamic Port Allocation for in-jvm dtest framework
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-18722
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18722
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/java
>            Reporter: Francisco Guerrero
>            Assignee: Francisco Guerrero
>            Priority: Normal
>             Fix For: 4.0.12, 4.1.4, 5.0, 5.0-alpha1, 5.x
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently, {{INodeProvisionStrategy}} supports two strategies 
> {{OneNetworkInterface}} and {{MultipleNetworkInterfaces}}. However the 
> {{seedPort}}, {{storagePorts}}, {{nativeTransportPorts}}, and {{jmxPorts}} 
> are always fixed or a function of the node number.
> In order to better support parallel test runs, we need to support dynamic 
> port allocation for the {{seedPort}}, {{storagePorts}}, 
> {{nativeTransportPorts}}, and {{jmxPorts}}. This would enable us to more 
> easily write tests that can run in parallel. This effort is only a stepping 
> stone in what's required to run more tests in parallel, but it allows us to 
> begin somewhere with the in-jvm dtest framework.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to