[
https://issues.apache.org/jira/browse/HADOOP-11984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549870#comment-14549870
]
Allen Wittenauer commented on HADOOP-11984:
-------------------------------------------
We set the MAVEN_OPTS to "-Xms256m -Xmx512m" in the development Dockerfile. So
I have zero confidence that the 3GB number represents what actually needs to be
used. As I've been digging through the precommit checks, there appears to be a
ton of bad design, bad decision making, or just plain old ignorance that's
been hanging around for a very long time. This feels like one of them. I
think it'd be worthwhile changing the precommit value, running some tests and
see what falls out. I suspect the answer will be: everything's fine.
> Enable parallel JUnit tests in pre-commit.
> ------------------------------------------
>
> Key: HADOOP-11984
> URL: https://issues.apache.org/jira/browse/HADOOP-11984
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-11984.001.patch, HADOOP-11984.002.patch,
> HADOOP-11984.003.patch, HADOOP-11984.004.patch, HADOOP-11984.005.patch
>
>
> HADOOP-9287 and related issues implemented the parallel-tests Maven profile
> for running JUnit tests in multiple concurrent processes. This issue
> proposes to activate that profile during pre-commit to speed up execution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
