Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 3774 invoked from network); 2 Jun 2008 06:24:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jun 2008 06:24:07 -0000 Received: (qmail 90018 invoked by uid 500); 2 Jun 2008 06:24:08 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 89979 invoked by uid 500); 2 Jun 2008 06:24:08 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 89968 invoked by uid 99); 2 Jun 2008 06:24:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Jun 2008 23:24:08 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 06:23:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F3705234C12D for ; Sun, 1 Jun 2008 23:23:44 -0700 (PDT) Message-ID: <1646324550.1212387824993.JavaMail.jira@brutus> Date: Sun, 1 Jun 2008 23:23:44 -0700 (PDT) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3151) Hod should have better error messages. In-Reply-To: <1508680323.1207084344315.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601532#action_12601532 ] Hadoop QA commented on HADOOP-3151: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12383075/HADOOP-3151 against trunk revision 661918. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no tests are needed for this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2532/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2532/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2532/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2532/console This message is automatically generated. > Hod should have better error messages. > -------------------------------------- > > Key: HADOOP-3151 > URL: https://issues.apache.org/jira/browse/HADOOP-3151 > Project: Hadoop Core > Issue Type: Bug > Components: contrib/hod > Affects Versions: 0.16.3 > Reporter: Arkady Borkovsky > Assignee: Vinod Kumar Vavilapalli > Fix For: 0.18.0 > > Attachments: HADOOP-3151 > > > (1) > gsgw1037:/homes/arkady/CDSR> hod allocate -n 4 -d xx > error: bin/hod failed to start. > error: invalid 'clusterdir' specified in section hod (--hod.clusterdir): xx > error: 1 problem found. > Check your command line options and/or your configuration file /grid/0/kryptonite/hod/conf/hodrc > * Directory 'xx' does not exist - the message shuold say "Non-existing directory" (or "directory not found"), not "invalid" > * checking the configuration file will not help, the advice is confusing > * checking the command line options is the obvious thing to do -- the advise is unnecessary. > (2) when hod does not understand the command, it prints the whole help options message -- which clobbers the screen and is confusing. It should give a meaningful message -- and may say "type hod help for more info" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.