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 4BA07187C7 for ; Mon, 14 Dec 2015 21:19:47 +0000 (UTC) Received: (qmail 4009 invoked by uid 500); 14 Dec 2015 21:19:47 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 3933 invoked by uid 500); 14 Dec 2015 21:19:46 -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 3896 invoked by uid 99); 14 Dec 2015 21:19:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2015 21:19:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B96732C1F6C for ; Mon, 14 Dec 2015 21:19:46 +0000 (UTC) Date: Mon, 14 Dec 2015 21:19:46 +0000 (UTC) From: "Jim Witschey (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-10863) HSHA test_closing_connections test still flaps on 3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jim Witschey created CASSANDRA-10863: ---------------------------------------- Summary: HSHA test_closing_connections test still flaps on 3.0 Key: CASSANDRA-10863 URL: https://issues.apache.org/jira/browse/CASSANDRA-10863 Project: Cassandra Issue Type: Bug Reporter: Jim Witschey Fix For: 3.0.x The problem reported in CASSANDRA-10570 still seems to be happening on CassCI, as recently as a couple days ago: http://cassci.datastax.com/job/cassandra-3.0_dtest/433/ [~carlyeks] The fix in #10570 was to increase how long we'd sleep in the tests. Should we just bump it up further, or does this make you suspect a larger problem here? -- This message was sent by Atlassian JIRA (v6.3.4#6332)