[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482572#comment-13482572
]
Hadoop QA commented on HADOOP-8661:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550509/HADOOP-8661.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1666//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1666//console
This message is automatically generated.
> RemoteException's Stack Trace would be better returned by getStackTrace
> -----------------------------------------------------------------------
>
> Key: HADOOP-8661
> URL: https://issues.apache.org/jira/browse/HADOOP-8661
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: HADOOP-8661.txt, HADOOP-8661.txt, HADOOP-8661.txt
>
>
> It looks like all exceptions produced by RemoteException include the full
> stack trace of the original exception in the message. This is different from
> 1.0 behavior to aid in debugging, but it would be nice to actually parse the
> stack trace and return it through getStackTrace instead of through getMessage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
