[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160728#comment-16160728
]
Hadoop QA commented on HADOOP-8661:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
3s{color} | {color:blue} The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HADOOP-8661 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-8661 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12550509/HADOOP-8661.txt |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/13239/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was 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-alpha1
>Reporter: Robert Joseph Evans
> Labels: BB2015-05-TBR
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946189#comment-15946189
]
Hadoop QA commented on HADOOP-8661:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
4s{color} | {color:blue} The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 12s{color}
| {color:red} HADOOP-8661 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-8661 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12550509/HADOOP-8661.txt |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/11974/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was 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-alpha1
>Reporter: Robert Joseph Evans
> Labels: BB2015-05-TBR
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081306#comment-15081306
]
Hadoop QA commented on HADOOP-8661:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m 1s
{color} | {color:blue} The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color}
| {color:red} HADOOP-8661 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12550509/HADOOP-8661.txt |
| JIRA Issue | HADOOP-8661 |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/8337/console |
This message was 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
> Labels: BB2015-05-TBR
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229180#comment-14229180
]
Hadoop QA commented on HADOOP-8661:
---
{color:red}-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 1556f86.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5131//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 was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
