cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7598) Dtest errors should show full system log message
Date Fri, 08 Aug 2014 17:05:12 GMT

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

Philip Thompson commented on CASSANDRA-7598:
--------------------------------------------

You'll see the dtests using python driver get similarly verbose debug logs:
http://cassci.datastax.com/job/cassandra-2.1_dtest_pydriver/52/testReport/

However, I don't think it covers the issue of getting the full stack trace from the node's
system.log

> 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)

Mime
View raw message