GitHub user srowen opened a pull request:

    https://github.com/apache/spark/pull/253

    SPARK-1335. Also increase perm gen / code cache for scalatest when invoked 
via Maven build

    I am observing build failures when the Maven build reaches tests in the new 
SQL components. (I'm on Java 7 / OSX 10.9). The failure is the usual complaint 
from scala, that it's out of permgen space, or that JIT out of code cache space.
    
    I see that various build scripts increase these both for SBT. This change 
simply adds these settings to scalatest's arguments. Works for me and seems a 
bit more consistent.
    
    (I also snuck in cures for new build warnings from new scaladoc. Felt too 
trivial for a new PR, although it's separate. Just something I also saw while 
examining the build output.)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/srowen/spark SPARK-1335

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/253.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #253
    
----
commit b2c6a099b9b1dd990f024a7657ce0ba53761b2c7
Author: Sean Owen <so...@cloudera.com>
Date:   2014-03-27T10:10:55Z

    Add perm gen, code cache settings to scalatest, mirroring SBT settings 
elsewhere, which allows tests to complete in at least one environment where 
they are failing. (Also removed a duplicate -Xms setting elsewhere.)

commit a02679cf15f36d652f48ceb4deb1a18e0bb10f23
Author: Sean Owen <so...@cloudera.com>
Date:   2014-03-27T10:11:41Z

    Fix scaladoc errors due to missing links, which are generating build 
warnings, from some recent doc changes. We apparently can't generate links 
outside the module.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to