Hadoop QA commented on YARN-2182:

{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 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 

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

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

This message is automatically generated.

> Update ContainerId#toString() to avoid conflicts before and after RM restart
> ----------------------------------------------------------------------------
>                 Key: YARN-2182
>                 URL: https://issues.apache.org/jira/browse/YARN-2182
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Tsuyoshi OZAWA
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-2182.1.patch, YARN-2182.2.patch
> ContainerId#toString() doesn't include any information about current cluster 
> id. This leads conflict between container ids. We can avoid the conflicts 
> without breaking backward compatibility by using epoch introduced on 
> YARN-2052.

This message was sent by Atlassian JIRA

Reply via email to