[
https://issues.apache.org/jira/browse/SPARK-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Wendell resolved SPARK-1798.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 732
[https://github.com/apache/spark/pull/732]
> Tests should clean up temp files
> --------------------------------
>
> Key: SPARK-1798
> URL: https://issues.apache.org/jira/browse/SPARK-1798
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.9.1
> Reporter: Sean Owen
> Priority: Minor
> Fix For: 1.0.0
>
>
> Three issues related to temp files that tests generate -- these should be
> touched up for hygiene but are not urgent.
> Modules have a log4j.properties which directs the unit-test.log output file
> to a directory like [module]/target/unit-test.log. But this ends up creating
> [module]/[module]/target/unit-test.log instead of former.
> The work/ directory is not deleted by "mvn clean", in the parent and in
> modules. Neither is the checkpoint/ directory created under the various
> external modules.
> Many tests create a temp directory, which is not usually deleted. This can be
> largely resolved by calling deleteOnExit() at creation and trying to call
> Utils.deleteRecursively consistently to clean up, sometimes in an "@After"
> method.
> (If anyone seconds the motion, I can create a more significant change that
> introduces a new test trait along the lines of LocalSparkContext, which
> provides management of temp directories for subclasses to take advantage of.)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
