[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-12 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/18921 Merged to master --- 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

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-12 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3890 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3890/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-12 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3890 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3890/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread pjfanning
Github user pjfanning commented on the issue: https://github.com/apache/spark/pull/18921 @srowen I had seen the mima issue on my local build but I wasn't sure if was just a local build issue. I have been able to get it to work locally by raising the sbt memory. --- If your project

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/18921 Hm, looks like MiMa is running out of memory for some reason now. I'm not so familiar with the `dev/mima` script but maybe the sbt call there can just increase the heap size? --- If your project

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3888 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3888/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3888 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3888/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3887 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3887/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/18921 **[Test build #3887 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3887/testReport)** for PR 18921 at commit

[GitHub] spark issue #18921: [SPARK-21709][Build] sbt 0.13.16 and some plugin updates

2017-08-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/18921 Can one of the admins verify this patch? --- 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