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

Hadoop QA commented on HADOOP-4112:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12389729/patch-4112.txt
  against trunk revision 693404.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3216/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3216/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3216/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3216/console

This message is automatically generated.

> Got ArrayOutOfBound exception while analyzing the job history
> -------------------------------------------------------------
>
>                 Key: HADOOP-4112
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4112
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Amar Kamat
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.19.0
>
>         Attachments: patch-4112.txt, patch-4112.txt
>
>
> HADOOP-3150 introduced 2 new type of tasks called the cleanup tasks. These 
> are logged to history either as map tasks or reduce tasks. The number of 
> maps/reducers is also logged to history. Since the number of maps will be 
> less than the total number of map tasks logged to history (actual num maps + 
> cleanup tasks), I think thats the reason for this exception. The important 
> question is to investigate the effect of HADOOP-3150 on job history and code 
> related to it.

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

Reply via email to