[
https://issues.apache.org/jira/browse/CASSANDRA-10686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068083#comment-15068083
]
Benjamin Lerer commented on CASSANDRA-10686:
--------------------------------------------
I agree that this fix will work. I just do not want to introduce some hacks in
the code unless the issue is a critical one. As the problem is a minor one, I
believe that we can wait for the proper fix.
People tend to forget to remove hacks and the code become less and less
readable and more and more difficult to maintain.
[~aholmber] could you make sure that
[PYTHON-458|https://datastax-oss.atlassian.net/browse/PYTHON-458] is addressed
reasonably quickly.
I am just in favor of fixing the DTests because flapping tests make us waist a
lot of time when we look in the CI results.
> cqlsh schema refresh on timeout dtest is flaky
> -----------------------------------------------
>
> Key: CASSANDRA-10686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10686
> Project: Cassandra
> Issue Type: Bug
> Components: Testing, Tools
> Reporter: Joel Knighton
> Assignee: Paulo Motta
> Priority: Minor
>
> [flaky 3.0
> runs|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> [flaky 2.2
> runs|http://cassci.datastax.com/job/cassandra-2.2_dtest/381/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> [flaky 2.1
> runs|http://cassci.datastax.com/job/cassandra-2.1_dtest/324/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> As far as I can tell, the issue could be with the test or the original issue.
> Pinging [~pauloricardomg] since he knows this best.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
