[
https://issues.apache.org/jira/browse/CASSANDRA-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091042#comment-14091042
]
Philip Thompson edited comment on CASSANDRA-7598 at 8/8/14 6:22 PM:
--------------------------------------------------------------------
Are we satisfied with a patch that shows the error followed by the next X lines
(15)? This should cover the stack trace and then some. Or would it be
preferable to only get the exact stack trace?
EDIT: I've opted for the latter. The code is much cleaner.
was (Author: philipthompson):
Are we satisfied with a patch that shows the error followed by the next X lines
(15)? This should cover the stack trace and then some. Or would it be
preferable to only get the exact stack trace?
> 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: Philip Thompson
>
> 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)
