Re: Tests failed after assembling the latest code from github

2014-04-15 Thread Aaron Davidson
By all means, it would be greatly appreciated! On Mon, Apr 14, 2014 at 10:34 PM, Ye Xianjin advance...@gmail.com wrote: Hi, I think I have found the cause of the tests failing. I have two disks on my laptop. The spark project dir is on an HDD disk while the tempdir created by

Re: Tests failed after assembling the latest code from github

2014-04-15 Thread Sean Owen
Good call -- indeed that same Files class has a move() method that will try to use renameTo() and then fall back to copy() and delete() if needed for this very reason. On Tue, Apr 15, 2014 at 6:34 AM, Ye Xianjin advance...@gmail.com wrote: Hi, I think I have found the cause of the tests

Re: Tests failed after assembling the latest code from github

2014-04-14 Thread Ye Xianjin
Thank you for your reply. After building the assembly jar, the repl test still failed. The error output is same as I post before. -- Ye Xianjin Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Tuesday, April 15, 2014 at 1:39 AM, Michael Armbrust wrote: I believe you may need an

Re: Tests failed after assembling the latest code from github

2014-04-14 Thread Ye Xianjin
Hi, I think I have found the cause of the tests failing. I have two disks on my laptop. The spark project dir is on an HDD disk while the tempdir created by google.io.Files.createTempDir is the /var/folders/5q/ ,which is on the system disk, an SSD. The ExecutorLoaderSuite test uses