Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 17 Oct 2011 16:36:11 +0000 (UTC)
From: "Hitesh Shah (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1087056782.1004.1318869371110.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1093066399.6484.1318450992224.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3176) ant mapreduce tests are timing
 out
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hitesh Shah commented on MAPREDUCE-3176:
----------------------------------------

bq. But before that. Hitesh, there are TODOs that you added in TestFileSytem, you intending to fix them?

Thanks Vinod for verifying. Yes, I planned to look at the test failure and fix it hence had marked the patch as a work in progress. There was a fix done to the command parser earlier which seems to have broken this particular test. 
                
> ant mapreduce tests are timing out
> ----------------------------------
>
>                 Key: MAPREDUCE-3176
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3176
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, test
>    Affects Versions: 0.23.0
>            Reporter: Ravi Prakash
>            Assignee: Hitesh Shah
>            Priority: Blocker
>              Labels: test
>             Fix For: 0.23.0
>
>         Attachments: MR-3176.wip.patch
>
>
> Secondary YARN builds started taking inordinately long and lots of tests started failing. Usually the secondary build would take ~ 2 hours. But recently even after 7 hours it wasn't done. 

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