Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 27 Oct 2011 20:44:32 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1225268035.26848.1319748272374.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1298648062.24999.1319727992460.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3281)
 TestLinuxContainerExecutorWithMocks failing on trunk.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on MAPREDUCE-3281:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #1252 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1252/])
    MAPREDUCE-3281. Fixed one more bug due to which TestLinuxContainerExecutorWithMocks was failing. (vinodkv)

vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1190007
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/mock-container-executor

                
> TestLinuxContainerExecutorWithMocks failing on trunk.
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-3281
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3281
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3281-20111027.txt, MAPREDUCE-3281-20111028.txt
>
>


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