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

Ekaterina Dimitrova edited comment on CASSANDRA-15588 at 11/17/20, 9:18 PM:
----------------------------------------------------------------------------

I think most of the Circle failures are because of resource issues. BUT [~mck] 
made it possible to run all of them in Jenkins where the failures are still a 
lot. I will actually try to look at them again. There were two big groups of 
failures. While looking into one of them, it disappeared (probably someone 
fixed something) :D But I have to check what was the other one if I can easily 
fix it and reduce the scope.


was (Author: e.dimitrova):
I think most of the Circle failures are because of resource issues. BUT [~mck] 
made it possible to run all of them in Jenkins where they are still a lot. I 
will actually try to look at them again. There were two big groups of failures. 
While looking into one of them, it disappeared (probably someone fixed 
something) :D But I have to check what was the other one if I can easily fix it 
and reduce the scope.

> 4.0 quality testing: Cluster Upgrade
> ------------------------------------
>
>                 Key: CASSANDRA-15588
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15588
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest/java, Test/dtest/python
>            Reporter: Josh McKenzie
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> We've historically had numerous bugs concerning upgrading clusters from one 
> version to the other. Let's establish the supported upgrade path and ensure 
> that users can safely perform the upgrades in production.



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