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 871A31856B for ; Mon, 22 Feb 2016 10:02:18 +0000 (UTC) Received: (qmail 88338 invoked by uid 500); 22 Feb 2016 10:02:18 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 88306 invoked by uid 500); 22 Feb 2016 10:02:18 -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 88250 invoked by uid 99); 22 Feb 2016 10:02:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2016 10:02:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 29B3E2C1F5D for ; Mon, 22 Feb 2016 10:02:18 +0000 (UTC) Date: Mon, 22 Feb 2016 10:02:18 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11196) tuple_notation_test upgrade tests flaps 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-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156712#comment-15156712 ] Sylvain Lebresne commented on CASSANDRA-11196: ---------------------------------------------- [~mambocab] Is there still no way to get the server logs from a failed job? Being able to would likely make this trivial (without it we'll need to reproduce locally so we get a proper server side trace) and would have been tremendously useful a lot of times. > tuple_notation_test upgrade tests flaps > --------------------------------------- > > Key: CASSANDRA-11196 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11196 > Project: Cassandra > Issue Type: Bug > Reporter: Jim Witschey > Assignee: Benjamin Lerer > Labels: dtest > > {{tuple_notation_test}} in the {{upgrade_tests.cql_tests}} module flaps on a number of different upgrade paths. Here are some of the tests that flap: > {code} > upgrade_tests/cql_tests.py:TestCQLNodes2RF1_2_1_UpTo_2_2_HEAD.tuple_notation_test > upgrade_tests/cql_tests.py:TestCQLNodes2RF1_2_1_UpTo_2_2_HEAD.tuple_notation_test > upgrade_tests/cql_tests.py:TestCQLNodes3RF3_2_1_UpTo_2_2_HEAD.tuple_notation_test > upgrade_tests/cql_tests.py:TestCQLNodes3RF3_2_1_UpTo_2_2_HEAD.tuple_notation_test > upgrade_tests/cql_tests.py:TestCQLNodes3RF3_2_2_HEAD_UpTo_Trunk.tuple_notation_test > upgrade_tests/cql_tests.py:TestCQLNodes3RF3_2_2_HEAD_UpTo_Trunk.tuple_notation_test > {code} > Here's an example failure: > http://cassci.datastax.com/job/upgrade_tests-all/9/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_2_1_UpTo_2_2_HEAD/tuple_notation_test/ > All the failures I've seen fail with this error: > {code} > > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)