Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 8 Aug 2014 17:45:14 +0000 (UTC)
From: "Michael Shuler (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12729191.1406130773543.44842.1407519914814@arcas>
In-Reply-To: <JIRA.12729191.1406130773543@arcas>
References: <JIRA.12729191.1406130773543@arcas>
Subject: [jira] [Commented] (CASSANDRA-7598) Dtest errors should show full
 system log message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091024#comment-14091024 ] 

Michael Shuler commented on CASSANDRA-7598:
-------------------------------------------

Your right - those are coming from the driver, not the node.  My mistake.

> Dtest errors should show full system log message
> ------------------------------------------------
>
>                 Key: CASSANDRA-7598
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7598
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ryan McGuire
>            Assignee: Ryan McGuire
>
> Although system errors are always reported when they happen, dtest does not show the full message. You have to go to the log file yourself to see the actual error. This takes two seconds when running a test by hand, but it's more difficult when viewing results run on cassci. We should be able to parse this out and pump it into the top most exception that is spit out by nosetests.
> Example of a useless error message: http://cassci.datastax.com/job/cassandra_upgrade_dtest/66/testReport/upgrade_through_versions_test/TestUpgradeThroughVersions/upgrade_test_2/


--
This message was sent by Atlassian JIRA
(v6.2#6252)