[
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.01.patch
Attaching a patch. Sample result:
{code}
|| Subsystem || Report/Notes ||
============================================================================
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12738174/HADOOP-12070.001.patch
|
| git revision | trunk / 63d0365 |
| Optional Tests | asflicense |
| uname | Linux localhost.localdomain 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr
22 06:48:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /home/sekikn/hadoop/dev-support/personality/hadoop.sh |
| Default Java | 1.7.0_79 |
| Max memory consumed | 108MB |
{code}
Is the subsystem name too long?
> 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
> 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)
