You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/07/09 11:40:04 UTC

[jira] [Commented] (HADOOP-12157) test-patch should report max memory consumed

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

Hadoop QA commented on HADOOP-12157:
------------------------------------

(!) A patch to the files used for the QA process has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at https://builds.apache.org/job/PreCommit-HADOOP-Build/7210/console in case of problems.

> test-patch should report max memory consumed
> --------------------------------------------
>
>                 Key: HADOOP-12157
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12157
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: yetus
>            Reporter: Allen Wittenauer
>            Assignee: Kengo Seki
>            Priority: Minor
>         Attachments: HADOOP-12157.HADOOP-12111.01.patch
>
>
> It would be nice if test-patch would look at the report that maven generates across all of the outputs to report how much memory was consumed and provide the max value.  This way MAVEN_OPTS could be set appropriately rather than the WAGs people make now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)