cassandra-commits mailing list archives

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

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

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

We might look at how the python-driver captures and exposes the system errors during nosetest
- i.e.:
(scroll down to find {{>> begin captured logging <<}})
http://cassci.datastax.com/job/y_python-driver_master-2.0.x/106/console
(not a fan of the newish {{\[nodeX ERROR\]}} lines, wherever those come from)

> 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