[
https://issues.apache.org/jira/browse/YARN-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980366#comment-13980366
]
Hadoop QA commented on YARN-1982:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641801/YARN-1982.1.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: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
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 .
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3625//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3625//console
This message is automatically generated.
> Rename the daemon name to timelineserver
> ----------------------------------------
>
> Key: YARN-1982
> URL: https://issues.apache.org/jira/browse/YARN-1982
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Labels: cli
> Attachments: YARN-1982.1.patch
>
>
> Nowadays, it's confusing that we call the new component timeline server, but
> we use
> {code}
> yarn historyserver
> yarn-daemon.sh start historyserver
> {code}
> to start the daemon.
> Before the confusion keeps being propagated, we'd better to modify command
> line asap.
--
This message was sent by Atlassian JIRA
(v6.2#6252)