[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92473419 [Test build #30188 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30188/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92453291 [Test build #30173 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30173/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92472629 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92453329 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92509801 [Test build #30198 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30198/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92505667 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92505634 [Test build #30188 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30188/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92509413 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92540457 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread davies
Github user davies commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92541203 I had triggered several runs in a row, waiting for the results. If they all passed, we could merge this. --- If your project is set up for it, you can reply to this

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92541148 [Test build #663 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/663/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92541260 [Test build #664 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/664/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92541125 [Test build #30208 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30208/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92540777 Alright, one last time. If this passes, I'd suggest re-enabling the test, so that if it's still flaky we can look at logs and figure out why. (I worked with Sean and have

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92556316 [Test build #663 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/663/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92549076 [Test build #665 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/665/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92556184 [Test build #664 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/664/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92533768 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92533725 [Test build #30198 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30198/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92553873 [Test build #30208 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30208/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92553890 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92424828 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-13 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92425507 [Test build #30173 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30173/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-12 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92204156 [Test build #30140 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30140/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-12 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92224717 [Test build #30140 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30140/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-12 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92224747 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-12 Thread rxin
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92202025 It just doesn't fail when you wanted it to fail! --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-12 Thread rxin
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-92201987 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91758926 [Test build #30066 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30066/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91758946 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread vanzin
GitHub user vanzin opened a pull request: https://github.com/apache/spark/pull/5459 WIP: re-enable flaky test to catch failure in jenkins. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vanzin/spark SPARK-6700 Alternatively

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91689597 [Test build #30048 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30048/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91708616 [Test build #30048 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30048/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91708629 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91709409 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91709944 [Test build #30055 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30055/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91724648 [Test build #30055 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30055/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91724655 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91724821 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91725061 [Test build #30061 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30061/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91736910 [Test build #30061 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30061/consoleFull) for PR 5459 at commit

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91736940 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread vanzin
Github user vanzin commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91748515 Jenkins, retest this please. --- 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

[GitHub] spark pull request: WIP: re-enable flaky test to catch failure in ...

2015-04-10 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/5459#issuecomment-91749048 [Test build #30066 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30066/consoleFull) for PR 5459 at commit