Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6148518F81 for ; Tue, 22 Dec 2015 13:11:53 +0000 (UTC) Received: (qmail 74299 invoked by uid 500); 22 Dec 2015 13:11:47 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 74282 invoked by uid 500); 22 Dec 2015 13:11:47 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 74271 invoked by uid 99); 22 Dec 2015 13:11:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2015 13:11:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B74A12C1F57 for ; Tue, 22 Dec 2015 13:11:46 +0000 (UTC) Date: Tue, 22 Dec 2015 13:11:46 +0000 (UTC) From: "Benjamin Lerer (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10686) cqlsh schema refresh on timeout dtest is flaky MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)