[
https://issues.apache.org/jira/browse/CASSANDRA-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341332#comment-17341332
]
Ekaterina Dimitrova commented on CASSANDRA-16613:
-------------------------------------------------
In a quick [Slack
discussion|https://the-asf.slack.com/archives/CK23JSY2K/p1620403646401500] I
was given the idea to move those two tests that now run longer to the long
tests so I don't have to raise the timeout for many classes because of two.
I just did it and final CI runs are here:
[4.0 patch|https://github.com/ekaterinadimitrova2/cassandra/tree/16613-4.0] |
[CI
run|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/755/#showFailuresLink]
[trunk patch|https://github.com/ekaterinadimitrova2/cassandra/tree/16613-trunk]
| [CI
run|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/754/#showFailuresLink]
One of them is marked as failed but when I open the link it says passed and it
passes locally so I think it should be fine.
I will commit it soon.
> ProtocolVersion.V4 is still used in places in the code
> ------------------------------------------------------
>
> Key: CASSANDRA-16613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16613
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.0-rc2, 4.0-rc
>
>
> While working on CASSANDRA-16567, [~adelapena] observed that
> _ProtocolVersion.V4_ is used in _ViewTest_.
> I decided to do a quick grep and observed a list of places where we still
> refer to V4 and it seems at least in many of the tests that was left not
> intentionally.
> This ticket is to verify the usage of _ProtocolVersion.V4_ in the codebase
> and bump it to V5 or default version, similar to what was done in
> CASSANDRA-16567, wherever there is a need.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
