[
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529514#comment-17529514
]
Josh McKenzie commented on CASSANDRA-17563:
-------------------------------------------
bq. I do have concerns for me to manually create a new MIDRES as that thing I
found out the hard way is brittle; hence this patch.
100% agree; hence my feedback about us making the UX a little clearer /
smoother for folks so the scripted creation becomes the One True Way going
forward.
Breaking out the "revert MIDRES to working state" from "make this less brittle
going forward" gets a +1 from me.
> 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]
