[
https://issues.apache.org/jira/browse/HADOOP-12157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kengo Seki updated HADOOP-12157:
--------------------------------
Attachment: HADOOP-12157.HADOOP-12111.05.patch
Thanks, I overlooked that case. Attaching a fixed patch.
If maxmem is empty, its row in the footer table is simply skipped.
Additionally, grep -o is rewritten by awk one-liner (HADOOP-12243).
> 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,
> HADOOP-12157.HADOOP-12111.02.patch, HADOOP-12157.HADOOP-12111.03.patch,
> HADOOP-12157.HADOOP-12111.04.patch, HADOOP-12157.HADOOP-12111.05.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)
