Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6392010A82 for ; Tue, 10 Feb 2015 18:05:14 +0000 (UTC) Received: (qmail 94327 invoked by uid 500); 10 Feb 2015 18:05:14 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 94268 invoked by uid 500); 10 Feb 2015 18:05:14 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 94253 invoked by uid 99); 10 Feb 2015 18:05:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 18:05:14 +0000 Date: Tue, 10 Feb 2015 18:05:13 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3164) rmadmin command usage prints incorrect command name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314544#comment-14314544 ] Hadoop QA commented on YARN-3164: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12697812/YARN-3164.1.patch against trunk revision 4eb5f7f. {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:red}-1 findbugs{color}. The patch appears to introduce 2 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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: org.apache.hadoop.ipc.TestRPCWaitForProxy org.apache.hadoop.yarn.client.api.impl.TestAMRMClient Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6577//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6577//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6577//console This message is automatically generated. > rmadmin command usage prints incorrect command name > --------------------------------------------------- > > Key: YARN-3164 > URL: https://issues.apache.org/jira/browse/YARN-3164 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.6.0 > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Priority: Minor > Attachments: YARN-3164.1.patch > > > /hadoop/bin>{color:red} ./yarn rmadmin -transitionToActive {color} > transitionToActive: incorrect number of arguments > Usage:{color:red} HAAdmin {color} [-transitionToActive [--forceactive]] > >{color:red} ./yarn HAAdmin {color} > Error: Could not find or load main class HAAdmin > Expected it should be rmadmin -- This message was sent by Atlassian JIRA (v6.3.4#6332)