[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641331#comment-14641331
]
Colin Patrick McCabe commented on HADOOP-12261:
-----------------------------------------------
[~alanburlison], did you try running the unit tests with {{\-Xmx2048m}}? If
that works, then it would be an easy solution to this issue.
[~aw], I disagree that the PMC is "completely untrustworthy" for occasionally
allowing incompatible changes in branch-2. Sometimes incompatible changes are
the only way forward that makes sense. For example, when we moved to JDK7,
very few users were still on JDK6 and we received no major complaints. I'm
sure there are things that we could do better (especially in the area of
stability) but let's try to keep this discussion constructive and focused on
the issue at hand.
If we can't easily fix the unit tests to run in 2048 megs, we should start a
thread on the dev and user list about whether running the unit tests under
32-bit should still be supported. (I'm not even talking about dropping support
for 32-bit deployments, but just for unit tests.)
> Surefire needs to make sure the JVMs it fires up are 64-bit
> -----------------------------------------------------------
>
> Key: HADOOP-12261
> URL: https://issues.apache.org/jira/browse/HADOOP-12261
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: test
> Affects Versions: 2.7.1
> Reporter: Alan Burlison
> Assignee: Alan Burlison
>
> hadoop-project/pom.xml sets maven-surefire-plugin.argLine to include
> -Xmx4096m. Allocating that amount of memory requires a 64-bit JVM, but on
> platforms with both 32 and 64-bit JVMs surefire runs the 32 bit version by
> default and tests fail to start as a result. "-d64" should be added to the
> command-line arguments to ensure a 64-bit JVM is always used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
