[
https://issues.apache.org/jira/browse/CASSANDRA-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156651#comment-16156651
]
Andrés de la Peña commented on CASSANDRA-13847:
-----------------------------------------------
Right, the bug also affects 2.1 and 2.2.
Here is the patch to solve it in 2.2 and the patch for dtests with the
{{@since}} tag:
||[2.2|https://github.com/apache/cassandra/compare/cassandra-2.2...adelapena:13847-2.2]||[dtest|https://github.com/apache/cassandra-dtest/compare/master...adelapena:13847]||
Regarding 2.1, I agree this is indeed insufficiently critical, and there's a
clear workaround (exiting cqlsh and logging back).
> test failure in
> cqlsh_tests.cqlsh_tests.CqlLoginTest.test_list_roles_after_login
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-13847
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13847
> Project: Cassandra
> Issue Type: Bug
> Components: Testing, Tools
> Reporter: Joel Knighton
> Labels: test-failure
> Fix For: 2.1.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest/546/testReport/cqlsh_tests.cqlsh_tests/CqlLoginTest/test_list_roles_after_login
> This test was added for [CASSANDRA-13640]. The comments seem to indicated
> this is only a problem on 3.0+, but the added test certainly seems to
> reproduce the problem on 2.1 and 2.2. Even if the issue does affect 2.1/2.2,
> it seems insufficiently critical for 2.1, so we need to limit the test to run
> on 2.2+ at the very least, possibly 3.0+ if we don't fix the cause on 2.2.
> Thoughts [~adelapena]?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
