[
https://issues.apache.org/jira/browse/TEZ-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389460#comment-14389460
]
Hadoop QA commented on TEZ-2216:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708515/TEZ-2216.1.patch
against master revision 3bfe003.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) 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 .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/376//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/376//console
This message is automatically generated.
> Expose errors during AM initialization
> --------------------------------------
>
> Key: TEZ-2216
> URL: https://issues.apache.org/jira/browse/TEZ-2216
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Attachments: TEZ-2216.1.patch
>
>
> If there are bad configs or other issues that cause errors/exceptions during
> AM initialization (eg. during service init) then those errors are not exposed
> to the user. Exposing them would be useful in quickly debugging such issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
