[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644920#comment-14644920
]
Alan Burlison commented on HADOOP-12261:
----------------------------------------
.bq Can you post the patch so that we can find out? Also, I can't +1 my own
patch, so I really do need you (as opposed to me) to post it. It's a procedural
thing...
I can but I have to take all patches through our internal legal approval
process before I can post them. I'm loathe to do that unless I know it's an
actual fix.
.bq I have observed it as well. I wonder why local test runs are flaky, but
Jenkins seems to be relatively predictable? Perhaps some tests can't run on
smaller machines?
What qualifies as "smaller"? And most of the errors I see aren't size-related,
they are various network-related timeouts and size/count mismatches, random
file creation issues and so forth.
> 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)
