[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643159#comment-14643159
]
Colin Patrick McCabe commented on HADOOP-12261:
-----------------------------------------------
Thanks, [~alanburlison]. Can you post the patch here? If it works on Jenkins,
I suppose we can commit it, and that will get 32-bit working again.
I agree that the difficulty of setting up a Hadoop test environment is a big
concern. If you have any ideas for improving it, that would be great. Perhaps
a docker image with a working setup would help? We also have a lot of tests
with too-tight timeouts or big resource requirements that tend to fail on
smaller build machines-- those should also be fixed.
[~aw], I was just pointing out that someday we will want to have a discussion
about the costs and benefits of 32-bit support. It looks like the proposed
change is minor, so we can postpone that day. I don't think your issues with
the PMC and the other folks on the project are relevant here and I would
appreciate it if you could stay focused.
> Surefire needs to make sure the JVMs it fires up fit within the memory
> available
> --------------------------------------------------------------------------------
>
> 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)
