[
https://issues.apache.org/jira/browse/MAPREDUCE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729413#action_12729413
]
Hadoop QA commented on MAPREDUCE-717:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12412839/717.patch
against trunk revision 792613.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+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 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/368/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/368/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/368/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/368/console
This message is automatically generated.
> Fix some corner case issues in speculative execution (post hadoop-2141)
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-717
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-717
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.21.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.21.0
>
> Attachments: 717.patch
>
>
> Some corner case issues can be fixed:
> 1) Setup task should not add anything to the job statistics (since they are
> really fast and might affect the statistics of a job with few tasks)
> 2) The statistics computations should be guarded for cases where things like
> sumOfSquares could become less than zero (due to rounding errors mostly).
> 3) The method TaskInProgress.getCurrentProgressRate() should take into
> account the COMMIT_PENDING state
> 4) The testcase TestSpeculativeExecution.testTaskLATEScheduling could be made
> more robust
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
