[
https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605171#comment-13605171
]
Hadoop QA commented on YARN-200:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12574150/YARN-200.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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/529//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 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
