[
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531417#comment-17531417
]
Ekaterina Dimitrova commented on CASSANDRA-17563:
-------------------------------------------------
Now when the CI and branches are back on track, I am going to rebase and run
again the patch with our brand new cassandra-4.1 and trunk. Commit pending CI
[4.1|https://github.com/apache/cassandra/compare/cassandra-4.1...ekaterinadimitrova2:16677-4.1?expand=1]
|
[CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=16677-4.1&filter=all]
[trunk
|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:trunk-17589?expand=1]|
[CI|
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=trunk-17589&filter=all]
> Fix CircleCI Midres config
> --------------------------
>
> Key: CASSANDRA-17563
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17563
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1.x
>
>
> During CircleCI addition of a new job to the config, the midres file got
> messy. Two of the immediate issues (but we need to verify all jobs will use
> the right executors and resources):
> * the new job needs to use higher parallelism as the original in-jvm job
> * j8_dtests_with_vnodes should get from midres 50 large but currently
> midres makes it run with 25 and medium which fails around 100 tests
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
