GitHub user vanzin opened a pull request:

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

    [minor] [build] Use custom temp directory during build.

    Even with all the efforts to cleanup the temp directories created by
    unit tests, Spark leaves a lot of garbage in /tmp after a test run.
    This change overrides java.io.tmpdir to place those files under the
    build directory instead.
    
    After an sbt full unit test run, I was left with > 400 MB of temp
    files. Since they're now under the build dir, it's much easier to
    clean them up.
    
    Also make a slight change to a unit test to make it not pollute the
    source directory with test data.

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

    $ git pull https://github.com/vanzin/spark unit-test-tmp

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

    https://github.com/apache/spark/pull/6653.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 #6653
    
----
commit aa9294498a3b44409547bb8cd631ff4209f6c016
Author: Marcelo Vanzin <[email protected]>
Date:   2015-06-04T20:35:51Z

    [minor] [build] Use custom temp directory during build.
    
    Even with all the efforts to cleanup the temp directories created by
    unit tests, Spark leaves a lot of garbage in /tmp after a test run.
    This change overrides java.io.tmpdir to place those files under the
    build directory instead.
    
    After an sbt full unit test run, I was left with > 400 MB of temp
    files. Since they're now under the build dir, it's much easier to
    clean them up.
    
    Also make a slight change to a unit test to make it not pollute the
    source directory with test data.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to