[ 
https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605608#comment-13605608
 ] 

Hadoop QA commented on YARN-200:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12574206/YARN-200.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 1 new 
or modified test files.

    {color:green}+1 tests included appear to have a timeout.{color}

    {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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

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

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

This message is automatically generated.
                
> yarn log does not output all needed information, and is in a binary format
> --------------------------------------------------------------------------
>
>                 Key: YARN-200
>                 URL: https://issues.apache.org/jira/browse/YARN-200
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 0.23.5
>            Reporter: Robert Joseph Evans
>            Assignee: Ravi Prakash
>              Labels: usability
>         Attachments: YARN-200.patch, YARN-200.patch
>
>
> yarn logs does not output attemptid, nodename, or container-id.  Missing 
> these makes it very difficult to look through the logs for failed containers 
> and tie them back to actual tasks and task attempts.
> Also the output currently includes several binary characters.  This is OK for 
> being machine readable, but difficult for being human readable, or even for 
> using standard tool like grep.
> The help message can also be more useful to users

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

Reply via email to