You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Balaji Rajagopalan (JIRA)" <ji...@apache.org> on 2010/08/02 09:40:22 UTC

[jira] Updated: (MAPREDUCE-1971) herriot automation system test case for verification of bug fix to jobhistory

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Balaji Rajagopalan updated MAPREDUCE-1971:
------------------------------------------

    Attachment: concurrent_y20_fix.patch

This fixes the issue with running the test case in secured env. 

> herriot automation system test case for verification of bug fix to jobhistory
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1971
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1971
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>         Environment: herriot 
>            Reporter: Balaji Rajagopalan
>         Attachments: concurrent_exp_y20.patch, concurrent_exp_y20_1.patch, concurrent_y20_fix.patch
>
>
> Run a few jobs and check the job history page .  Job history information should be displayed properly  . 
> Analyze a running job . The values shown in the page should be correct . 
> Concurrently access jobs in job history page . No exception should be thrown. 
> In the developed herriot test case accesses the job tracker tracker directly, the jsp page access does the same.  	

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