Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 75D7AEA35 for ; Thu, 17 Jan 2013 15:28:16 +0000 (UTC) Received: (qmail 42300 invoked by uid 500); 17 Jan 2013 15:28:15 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 42066 invoked by uid 500); 17 Jan 2013 15:28:15 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 41832 invoked by uid 99); 17 Jan 2013 15:28:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 15:28:14 +0000 Date: Thu, 17 Jan 2013 15:28:14 +0000 (UTC) From: "Aleksey Gorshkov (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-9219) coverage fixing for org.apache.hadoop.tools.rumen 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/HADOOP-9219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated HADOOP-9219: ------------------------------------- Attachment: HADOOP-9219-trunk.patch > coverage fixing for org.apache.hadoop.tools.rumen > ------------------------------------------------- > > Key: HADOOP-9219 > URL: https://issues.apache.org/jira/browse/HADOOP-9219 > Project: Hadoop Common > Issue Type: Test > Components: tools > Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 > Reporter: Aleksey Gorshkov > Fix For: 3.0.0, 2.0.3-alpha, 0.23.6 > > Attachments: HADOOP-9219-trunk.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > coverage fixing for org.apache.hadoop.tools.rumen > HADOOP-9219-trunk.patch for trunk, brunch-2 and branch-0.23 > patch checker reports about errors like: > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/log/megacluster.megacorp.com_1265616107882_job_201002080801_50510_conf.xml > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/log/megacluster.megacorp.com_1265616107882_job_201002080801_50510_job_name-DAILY%2F20100208%5D > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/log/megacluster.megacorp.com_1265616107882_job_201002080801_40864_job_name-DAILY%2F20100210%5D > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/log/megacluster.megacorp.com_1265616107882_job_201002080801_40864_conf.xml > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/data/19-jobs.trace > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/data/19-jobs.topology > !????? /home/jenkins/jenkins/workspace/Hadoop-common-FB-Patch-Verification-trunk-fb-YAHOO-163-trunk-gd/hadoop-common/hadoop-tools/hadoop-rumen/src/test/resources/data/job_1329348432655_0001-1329348443227-user-Sleep+job-1329348468601-10-1-SUCCEEDED-default.jhist > Lines that start with ????? in the release audit report indicate files that do not have an Apache license header. > This is data files and addition the license information corrupts test. -- 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