Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 12 Apr 2012 21:45:19 +0000 (UTC)
From: "Eli Collins (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1421601670.19495.1334267119602.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2030838412.16203.1334210918096.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-4142) MR test failures on branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252877#comment-13252877 ] 

Eli Collins commented on MAPREDUCE-4142:
----------------------------------------

bq. Note that was using ant 1.8.2, I switched to use ant 1.7.1 and it honored the ignore:

Thanks Thomas.  I'm using ant 1.8.2 as well, this a known issue with ant?
                
> MR test failures on branch-1
> ----------------------------
>
>                 Key: MAPREDUCE-4142
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4142
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Eli Collins
>            Assignee: Thomas Graves
>
> The following test classes are failing on branch-1: TestJobTrackerRestartWithLostTracker, TestJobTrackerSafeMode, TestMiniMRMapRedDebugScript, TestRecoveryManager, TestTaskTrackerLocalization.
> Recent MR changes, believe these tests were passing before these failures:
> - MAPREDUCE-4012 Hadoop Job setup error leaves no useful info to users. (tgrav
> - MAPREDUCE-1238. mapred metrics shows negative count of waiting maps and redu
> - MAPREDUCE-4017. Add jobname to jobsummary log (tgraves and Koji Noguchi via 
> - MAPREDUCE-4003. log.index (No such file or directory) AND Task process exit 
>     

--
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