[
https://issues.apache.org/jira/browse/MAPREDUCE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883460#action_12883460
]
Balaji Rajagopalan commented on MAPREDUCE-1899:
-----------------------------------------------
+ while (!jInfo.getStatus().isJobComplete()) {
+ UtilsForTests.waitFor(100);
+ jInfo = remoteJTClient.getJobInfo(jobId);
+ }
Please use the building block that I will check in shortly for the above code.
I agree with iyappan testjar has many failedmapper class that can be reused
instead of writing your own.
> [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.
