You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2008/09/09 21:57:44 UTC
[jira] Commented: (HADOOP-4129) Memory limits of TaskTracker and
Tasks should be in kiloBytes.
[ https://issues.apache.org/jira/browse/HADOOP-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629586#action_12629586 ]
Hadoop QA commented on HADOOP-4129:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389746/HADOOP-4129
against trunk revision 693524.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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 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/3220/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3220/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3220/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3220/console
This message is automatically generated.
> Memory limits of TaskTracker and Tasks should be in kiloBytes.
> --------------------------------------------------------------
>
> Key: HADOOP-4129
> URL: https://issues.apache.org/jira/browse/HADOOP-4129
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Vinod K V
> Assignee: Vinod K V
> Priority: Blocker
> Attachments: HADOOP-4129
>
>
> HADOOP-3759 uses memory limits in kilo-bytes and HADOOP-3581 changed it to be in bytes. Because of this, TestHighRAMJobs is failing on Linux. We should change this behaviour so that all memory limits are considered to be in kilo-bytes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.