[
https://issues.apache.org/jira/browse/YARN-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790363#comment-13790363
]
Hadoop QA commented on YARN-879:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607557/YARN-879-v5.1.patch
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 5 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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2153//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2153//console
This message is automatically generated.
> Fix tests w.r.t o.a.h.y.server.resourcemanager.Application
> ----------------------------------------------------------
>
> Key: YARN-879
> URL: https://issues.apache.org/jira/browse/YARN-879
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: YARN-879.patch, YARN-879-v2.patch, YARN-879-v3.patch,
> YARN-879-v4.patch, YARN-879-v5.1.patch, YARN-879-v5.patch
>
>
> getResources() will return a list of containers that allocated by RM.
> However, it is now return null directly. The worse thing is: if LOG.debug is
> enabled, then it will definitely cause NPE exception.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
