Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 941019B69 for ; Sun, 25 Mar 2012 04:14:09 +0000 (UTC) Received: (qmail 10536 invoked by uid 500); 25 Mar 2012 04:14:09 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 10297 invoked by uid 500); 25 Mar 2012 04:14:07 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 10243 invoked by uid 99); 25 Mar 2012 04:14:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2012 04:14:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2012 04:14:03 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 0BA00345479 for ; Sun, 25 Mar 2012 04:13:43 +0000 (UTC) Date: Sun, 25 Mar 2012 04:13:43 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1275048754.14015.1332648823069.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <2086470130.33112.1332192458300.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3116) Typo in fetchdt error message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237771#comment-13237771 ] Hadoop QA commented on HDFS-3116: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12519840/HDFS-3116.txt against trunk revision . +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 new tests are needed for this patch. Also please list what manual steps were performed to verify 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 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.tools.TestDFSHAAdmin org.apache.hadoop.hdfs.TestGetBlocks org.apache.hadoop.hdfs.tools.TestDFSHAAdminMiniCluster org.apache.hadoop.cli.TestHDFSCLI +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2093//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2093//console This message is automatically generated. > Typo in fetchdt error message > ----------------------------- > > Key: HDFS-3116 > URL: https://issues.apache.org/jira/browse/HDFS-3116 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client > Affects Versions: 0.24.0 > Reporter: Aaron T. Myers > Assignee: AOE Takashi > Priority: Trivial > Labels: newbie > Attachments: HDFS-3116.txt > > > In {{DelegationTokenFetcher.java}} there's the following typo of the word "exactly": > {code} > System.err.println("ERROR: Must specify exacltly one token file"); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira