[
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530294#comment-17530294
]
Ekaterina Dimitrova commented on CASSANDRA-17563:
-------------------------------------------------
For the record, this was a merge patch but the midres changes were done only
for trunk. No issue with previous branches.
Also, noticed all in_jvm for midres have to be large, p10. J11 was left
medium. Checked the old records where large was decided.
So the current patch reverts the two additional changes we see in MIDRES after
adding the new job plus raise to large the J11 in_jvm.
[Patch|https://github.com/ekaterinadimitrova2/cassandra/pull/new/CASSANDRA-16677-trunk],
[CI|
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=CASSANDRA-16677-trunk&filter=all]
just started
> 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]
