Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Thu, 22 Dec 2011 17:41:30 +0000 (UTC)
From: "Benoy Antony (Created) (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <803711358.39806.1324575690816.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-3594) Contrib/Streaming - Test
 org.apache.hadoop.streaming.TestUlimit fails on VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Contrib/Streaming - Test org.apache.hadoop.streaming.TestUlimit fails on VM
---------------------------------------------------------------------------

                 Key: MAPREDUCE-3594
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3594
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: contrib/streaming
    Affects Versions: 0.22.0
         Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
            Reporter: Benoy Antony
            Priority: Minor


The TestUlimit test is as follows : 

The testcse sets the upper limit for virtual memory to 768 MB in the jobconf 
Start a maponly job. 
Let the task get the applicable ulimit from the shell and write it as the output. 
The testcase will wait for the completion of the job and compare the joboutput with the ulimit originally set in the jobconf 

But this testcase fails because all the task attempts fail with the following exception 

java.lang.Throwable: Child Error 
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:225) 
Caused by: java.io.IOException: Task process exit with nonzero status of 134. 
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:212) 

So there is no job output . 

The Test passes on my developer machine, but fails on the build machine which is a VM. The build machine OS is Red Hat Enterprise Linux Server release 6.1 (Santiago)

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