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

Ekaterina Dimitrova commented on CASSANDRA-17563:
-------------------------------------------------

My previous point still stands that we need to be sure everything on all 
branches works as before. 

IMHO what we really need to see is that every new highres and midres on every 
branch has only an addition of a new job in_jvm which match as resource usage 
the old single in_jvm job and no other changes applied. 

Thanks for all the updates and adding the docs, etc. I understand and really 
appreciate your good intentions for improvement and ease of maintenance. 
Unfortunately, I have a few immediate concerns w which make me think we need to 
have immediate fix for midres and rewrites of the scripts after the release:
 * There are changes to the other generate.sh script I haven't looked at but 
any change there need to be tested that it didn't break any of the options 
added and tested one by one by [~adelapena] 
 * My concern is we don't know who was using what and how and it was working 
fine for quite some time. Do we want to rewrite the whole approach one week 
before freeze when people highly utilize CI to push their latest work? What do 
others think?
 * Also, now we will have a mix of python and shell scripts, are we sure the 
community will accept that? 

I really like and appreciate how you added diff but I am confused  from the 
output what I am seeing actually. I see the new name and resource change.

 

> 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]

Reply via email to