Hadoop QA commented on YARN-2224:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {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}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 

    {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 

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4125//console

This message is automatically generated.

> Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective 
> of the default settings
> -----------------------------------------------------------------------------------------------------
>                 Key: YARN-2224
>                 URL: https://issues.apache.org/jira/browse/YARN-2224
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-2224.patch
> If the default setting DEFAULT_NM_VMEM_CHECK_ENABLED is set to false the test 
> will fail. Make the test pass not rely on the default settings but just let 
> it verify that once the setting is turned on it actually does the memory 
> check. See YARN-2225 which suggests we turn the default off.

This message was sent by Atlassian JIRA

Reply via email to