[
https://issues.apache.org/jira/browse/HADOOP-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710299#action_12710299
]
Hadoop QA commented on HADOOP-5570:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12408234/HADOOP-5570-20090615.txt
against trunk revision 775492.
+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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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/Hadoop-Patch-vesta.apache.org/345/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/345/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/345/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/345/console
This message is automatically generated.
> TaskMemoryManager should log process-tree's status while killing tasks.
> -----------------------------------------------------------------------
>
> Key: HADOOP-5570
> URL: https://issues.apache.org/jira/browse/HADOOP-5570
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Vinod K V
> Assignee: Vinod K V
> Attachments: HADOOP-5570-20090614.txt, HADOOP-5570-20090615.txt
>
>
> This helps a lot in debugging why a particular task has gone beyond memory
> limits.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
