hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5068) testClusterBlockingForLackOfMemory in TestCapacityScheduler fails randomly
Date Wed, 04 Mar 2009 00:34:56 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678524#action_12678524
] 

Raghu Angadi commented on HADOOP-5068:
--------------------------------------

Is this committed? Many hudson builds are failing with the following in this test :

{noformat}
org.apache.hadoop.mapred.TestCapacityScheduler.testClusterBlockingForLackOfMemory

java.lang.NullPointerException
	at org.apache.hadoop.mapred.JobInProgress.garbageCollect(JobInProgress.java:2454)
	at org.apache.hadoop.mapred.JobInProgress.terminateJob(JobInProgress.java:2133)
	at org.apache.hadoop.mapred.JobInProgress.terminate(JobInProgress.java:2148)
	at org.apache.hadoop.mapred.JobInProgress.kill(JobInProgress.java:2216)
	at org.apache.hadoop.mapred.TestCapacityScheduler$FakeTaskTrackerManager.killJob(TestCapacityScheduler.java:359)
	at org.apache.hadoop.mapred.TestCapacityScheduler.testClusterBlockingForLackOfMemory(TestCapacityScheduler.java:2070)
{noformat}

Please commit the patch if it is ready.



> testClusterBlockingForLackOfMemory in TestCapacityScheduler fails randomly
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-5068
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5068
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>            Reporter: Sreekanth Ramakrishnan
>            Assignee: Vinod K V
>         Attachments: HADOOP-5068-20090120-git.txt, HADOOP-5068-20090121-git-1.txt, HADOOP-5068-20090121-git.txt
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> testClusterBlockingForLackOfMemory fails randomly when TestCapacityScheduler is run.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message