[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665548#comment-13665548
]
Hadoop QA commented on HADOOP-9593:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12584556/HADOOP-9593-002.patch
against trunk revision .
{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}. 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/2561//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2561//console
This message is automatically generated.
> stack trace printed at ERROR for all yarn clients without hadoop.home set
> -------------------------------------------------------------------------
>
> Key: HADOOP-9593
> URL: https://issues.apache.org/jira/browse/HADOOP-9593
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch
>
>
> This is the problem of HADOOP-9482 now showing up in a different application
> -one whose log4j settings haven't turned off all Shell logging.
> Unless you do that, all yarn clients will have a stack trace at error in
> their logs, which is generating false alarms and is utterly pointless. Why
> does this merit a stack trace? Why log it at error? It's not an error for a
> client app to not have these values set as long as they have the relevant
> JARs on their classpath. And if they don't, they'll get some classpath error
> instead
--
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
