[
https://issues.apache.org/jira/browse/MAPREDUCE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883454#action_12883454
]
Iyappan Srinivasan commented on MAPREDUCE-1899:
-----------------------------------------------
1) verfiyJobSummaryInfo method - typo. make "verfiy" as "verify" Correct in
calling places too.
2) FailMapper is not needed to be defined seperately as there is a
FailedMapper class already present in GenerateTaskChildProcess.java
3) testJobQueueInfoInJobSummary - Make sure that the comments on top of
testcase tell that job is submitted from a differnt queue.
4) testJobSummaryInfoOfHighMemoryJob - Make the comement as "high RAM" isntead
fo "high ram", just to be clear.
5) testJobSummaryInfoOfFailedJob -
+ Assert.assertEquals("Job has not been succeeded",
- This comment should be "Job has not failed as expected. but has succeeded"
> [Herriot] Test jobsummary information for different jobs.
> ---------------------------------------------------------
>
> Key: MAPREDUCE-1899
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1899
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: test
> Reporter: Vinay Kumar Thota
> Assignee: Vinay Kumar Thota
> Attachments: 1899-ydist-security.patch
>
>
> Test the following scenarios.
> 1. Verify the job summary information for killed job.
> 2. Verify the job summary information for failed job.
> 3. Verify the job queue information in job summary after job has successfully
> completed.
> 4. Verify the job summary information for high ram jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
