[
https://issues.apache.org/jira/browse/MAPREDUCE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833818#action_12833818
]
Vinod K V commented on MAPREDUCE-1093:
--------------------------------------
bq. This patch disables the failing assert in TestTaskTrackerMemoryManager.
Instead can we just let it be and file a new issue, attaching any test logs if
possible there? I quickly looked at the code and seemed that it should work the
way it is expressed in code.
So, I am leaning towards letting it be and going ahead with MAPREDUCE-1092. If
you already have some logs, you can create a new issue rightaway; I can look
into it..
> Java assertion failures triggered by tests
> ------------------------------------------
>
> Key: MAPREDUCE-1093
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1093
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Reporter: Eli Collins
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1093.patch
>
>
> While running the tests with java asserts enabled the following two asserts
> fired:
> {code}
> testStateRefresh in TestQueueManager:
> try{
> Job job = submitSleepJob(10, 2, 10, 10, true,null, "default" );
> assert(job.isSuccessful()); <==========
> }catch(Exception e){
> {code}
> {code}
> runJobExceedingMemoryLimit in TestTaskTrackerMemoryManager:
> for (TaskCompletionEvent tce : taskComplEvents) {
> // Every task HAS to fail
> assert (tce.getTaskStatus() == TaskCompletionEvent.Status.TIPFAILED ||
> tce <==========
> .getTaskStatus() == TaskCompletionEvent.Status.FAILED);
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
