[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641368#comment-14641368
]
Allen Wittenauer commented on HADOOP-12261:
-------------------------------------------
bq. I disagree that the PMC is "completely untrustworthy" for occasionally
allowing incompatible changes in branch-2.
Yes, you're right. I should be totally forgiving of the data loss, broken
jobs, lost functionality, and angry end users caused by these occasional (34 in
branch-2 since 2.3.0, including the 9 in 2.8.0 already)
actually-marked-as-incompatible changes. (Who knows how many more have slipped
through the cracks).
bq. let's try to keep this discussion constructive and focused on the issue at
hand.
Fine. It won't matter anyway. PMC members always use the "we broke JDK6 so
now we can do anything" excuse for every incompatible change, so we'll drop
32-bit in 2.8.0 regardless of the end user impact.
> 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)
