[
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526048#comment-17526048
]
Ekaterina Dimitrova commented on CASSANDRA-17563:
-------------------------------------------------
Thanks, so now everything will be the same in the setup, [~dcapwell] only adds
a tool to help to create new patches with minimum efforts. If someone prefers
to do it manually - that is fine. In all cases we need to verify after that the
generated MIDRES and HIGHRES files have exactly what we want for "happy" CI :D
The only thing to be mentioned is that the tool might rearrange the attributes,
so if someone feels bad about that, they can just use the old way and skip
seeing those rearrangements being just additional noise.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
