[ 
https://issues.apache.org/jira/browse/HADOOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534015
 ] 

Hadoop QA commented on HADOOP-2022:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12367562/HADOOP-2022.patch
against trunk revision r583424.

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

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

    javac +1.  The applied patch does not generate any new compiler warnings.

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

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

    contrib tests -1.  The patch failed contrib unit tests.

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

This message is automatically generated.

> Task times are not saved correctly (bug in hadoop-1874)
> -------------------------------------------------------
>
>                 Key: HADOOP-2022
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2022
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Devaraj Das
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-2022.patch
>
>
> In HADOOP-1874, a new taskstatus object is created for successful tasks. 
> However, in the new taskstatus object, the timestamps for the start/end of 
> the various phases are not filled. In the new status object, the timestamps 
> should be set from the old status object. The problem can be easily seen if 
> the taskdetails.jsp is accessed.

-- 
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