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

Ekaterina Dimitrova edited comment on CASSANDRA-16489 at 3/5/21, 6:21 PM:
--------------------------------------------------------------------------

Thanks [~samt], I made a pass and I have only one question, we don't have to 
patch utests_system_keyspace_directory for higher resources, they are fine with 
medium resources? I mean for LOWRES and MIIDRES probably we are good as that is 
how the tests were added initially. But I wasn't sure whether you guys want 
them on HIGHRES on your end?

Maybe it is a good idea to trigger one clean run?


was (Author: e.dimitrova):
Thanks [~samt], I made a pass and I have only one question, we don't have to 
patch utests_system_keyspace_directory for higher res, they are fine with 
medium resources? I mean for LOWRES and MIIDRES probably we are good as that is 
how the tests were added initially. But I wasn't sure whether you guys want 
them on HIGHRES on your end?

Maybe it is a good idea to trigger one clean run?

> Add utest_system_keyspace_directory to CircleCI config template
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-16489
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16489
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 4.0
>
>
> In CASSANDRA-14793 a new circle job config was added directly to the CircleCI 
> base, LOWRES, MIDRES and HIGHRES config files, but not to the template file. 
> When the config was regenerated for CASSANDRA-16474, the new job was lost. We 
> should restore it and add it to the config template to avoid any reoccurrence.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to