Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12855#issuecomment-219635725
**[Test build #58666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58666/consoleFull)**
for PR 12855 at commit
[`5f780a7`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219635907
**[Test build #58671 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58671/consoleFull)**
for PR 13099 at commit
[`7ff2021`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12855#issuecomment-219635877
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219635957
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12855#issuecomment-219635881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219635956
Merged build finished. Test PASSed.
---
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 projec
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219636678
LGTM. Merged into master and branch-2.0. Thanks!
---
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 user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13099
---
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 ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219638216
**[Test build #58673 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58673/consoleFull)**
for PR 13129 at commit
[`645f6c4`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13095#issuecomment-219639437
**[Test build #58667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58667/consoleFull)**
for PR 13095 at commit
[`06f89d5`](https://g
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63474760
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -239,10 +239,7 @@ class GeneralizedLinearRegressio
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13095#issuecomment-219639674
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13095#issuecomment-219639672
Merged build finished. Test PASSed.
---
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 projec
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63475090
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -252,7 +250,7 @@ class LinearRegression @Since("1.3.0") (@Sinc
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13138#issuecomment-219640461
**[Test build #58669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58669/consoleFull)**
for PR 13138 at commit
[`5da31c9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13138#issuecomment-219640714
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13138#issuecomment-219640717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13037#issuecomment-219644740
I share the concern. Some info has been added piecemeal such that it is
somewhat cluttered. This change isn't the one that breaks the camel's back so
to speak. Any easy
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219646199
**[Test build #58673 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58673/consoleFull)**
for PR 13129 at commit
[`645f6c4`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219646342
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-219646339
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219647993
**[Test build #58674 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58674/consoleFull)**
for PR 12627 at commit
[`e9841ff`](https://gi
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/12870
---
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 ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219650199
**[Test build #58675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58675/consoleFull)**
for PR 12939 at commit
[`f2b7adb`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-219650730
**[Test build #58672 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58672/consoleFull)**
for PR 13142 at commit
[`13c26ff`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-219650978
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-219650975
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-219651320
**[Test build #58676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58676/consoleFull)**
for PR 12257 at commit
[`0bb2924`](https://gi
Github user jurriaan commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219653230
@liancheng What do you think?
---
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
GitHub user devaraj-kavali opened a pull request:
https://github.com/apache/spark/pull/13143
[SPARK-15359] [Mesos] Mesos dispatcher should handle DRIVER_ABORTED status
from mesosDriver.run()
## What changes were proposed in this pull request?
When the mesosDriver.run() retu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13143#issuecomment-219654599
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 p
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/13144
[SPARK-14346][SQL][follow-up] add tests for CREAT TABLE USING with
partition and bucket
## What changes were proposed in this pull request?
https://github.com/apache/spark/pull/12781 int
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13144#issuecomment-219657164
CC @yhuai @liancheng
---
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 th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13144#issuecomment-219657960
**[Test build #58677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58677/consoleFull)**
for PR 13144 at commit
[`59b0866`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13074#issuecomment-219658693
Merged to master/2.0
---
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 f
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13074
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13042#issuecomment-219659234
I'm OK with just the first change, for tidiness.
---
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 user srowen commented on the pull request:
https://github.com/apache/spark/pull/13110#issuecomment-219659650
The Rating _case class_ was not removed, just the _object_. The Java
example has no equivalent and is OK as-is.
---
If your project is set up for it, you can reply to t
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13138#issuecomment-219660475
merging to master and 2.0!
---
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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13138
---
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 ena
Github user mouendless commented on the pull request:
https://github.com/apache/spark/pull/13133#issuecomment-219661119
@srowen progress report. I finally fix my scala style plugin. I ran it and
fixed the reported style issues ,and compile, please check again. Though the
code can be s
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219661237
**[Test build #58678 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58678/consoleFull)**
for PR 13008 at commit
[`0fd8a90`](https://gi
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/13145
[MINOR][SQL] Remove unused pattern matching variables in Optimizers.
## What changes were proposed in this pull request?
This PR removes unused pattern matching variable in Optimizers
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219662340
**[Test build #58680 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58680/consoleFull)**
for PR 13008 at commit
[`225128d`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219662330
**[Test build #58679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58679/consoleFull)**
for PR 13145 at commit
[`007b7c9`](https://gi
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13079#discussion_r63488949
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -626,40 +626,142 @@ case class ShowCreateTableCommand(table:
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13079#discussion_r63489023
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -626,40 +626,142 @@ case class ShowCreateTableCommand(table:
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13079#discussion_r63488983
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
---
@@ -95,7 +101,8 @@ case class CatalogTable(
prope
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13079#discussion_r63489049
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -626,40 +626,142 @@ case class ShowCreateTableCommand(table:
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13079#discussion_r63489249
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -626,40 +626,142 @@ case class ShowCreateTableCommand(table:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219664603
**[Test build #58680 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58680/consoleFull)**
for PR 13008 at commit
[`225128d`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219664629
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219664628
Merged build finished. Test FAILed.
---
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 projec
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12719#discussion_r63491368
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -659,6 +660,45 @@ object NullPropagation extends Rule
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12719#discussion_r63491459
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -659,6 +660,45 @@ object NullPropagation extends Rule
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219668576
Mostly LGTM except some minor comments, thanks for working on it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219669729
**[Test build #58675 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58675/consoleFull)**
for PR 12939 at commit
[`f2b7adb`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219669830
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219669778
**[Test build #58678 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58678/consoleFull)**
for PR 13008 at commit
[`0fd8a90`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-219669826
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219669982
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12939#issuecomment-219669985
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219670004
Thank YOU, @cloud-fan . I fix them soon.
---
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 p
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13045#issuecomment-219670131
I don't have a good idea either, one possible approach is improving
`UnresolvedAlias` to take a function as the optional alias name, and the
function will take the re
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/13146
[SPARK-13081][PYSPARK][SPARK_SUBMIT]. Allow set pythonExec of driver and
executor through confâ¦
## What changes were proposed in this pull request?
(Please fill in changes proposed in thi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13146#issuecomment-219671444
**[Test build #58681 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58681/consoleFull)**
for PR 13146 at commit
[`62db330`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219672566
**[Test build #58682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58682/consoleFull)**
for PR 12627 at commit
[`9d25eba`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219672925
**[Test build #58674 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58674/consoleFull)**
for PR 12627 at commit
[`e9841ff`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219673118
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219673115
Merged build finished. Test FAILed.
---
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 projec
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/13147
[SPARK-6320][SQL] Move planLater method into GenericStrategy.
## What changes were proposed in this pull request?
This PR moves `QueryPlanner.planLater()` method into `GenericStrategy` for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13147#issuecomment-219673646
**[Test build #58683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58683/consoleFull)**
for PR 13147 at commit
[`e7554f0`](https://gi
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13145#discussion_r63496130
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -440,10 +439,10 @@ object ColumnPruning extends Rule[Log
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/13148
[SPARK-15361] [ML] ML 2.0 QA: Scala APIs audit for clustering
## What changes were proposed in this pull request?
Audit Scala API for ml.clustering.
Fix some wrong API documentations and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219675819
**[Test build #58670 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58670/consoleFull)**
for PR 13099 at commit
[`7ff2021`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219675841
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219675843
**[Test build #58684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58684/consoleFull)**
for PR 13148 at commit
[`de584aa`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219675846
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13144#issuecomment-219676184
**[Test build #58677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58677/consoleFull)**
for PR 13144 at commit
[`59b0866`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13144#issuecomment-219676432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13144#issuecomment-219676428
Merged build finished. Test PASSed.
---
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 projec
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219677538
Looks reasonable, but I wonder if this should be done at once for all of
the code base?
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13133#discussion_r63498672
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/LocalKMeans.scala ---
@@ -66,6 +64,12 @@ private[mllib] object LocalKMeans extends Logging {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13133#discussion_r63498667
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/LocalKMeans.scala ---
@@ -46,17 +46,15 @@ private[mllib] object LocalKMeans extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-219679298
**[Test build #58676 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58676/consoleFull)**
for PR 12257 at commit
[`0bb2924`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-219679554
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-219679552
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219680042
**[Test build #58685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58685/consoleFull)**
for PR 12719 at commit
[`97afe31`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219681064
**[Test build #58686 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58686/consoleFull)**
for PR 12719 at commit
[`d69f521`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219681780
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219681775
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219681748
**[Test build #58685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58685/consoleFull)**
for PR 12719 at commit
[`97afe31`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219682317
**[Test build #58679 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58679/consoleFull)**
for PR 13145 at commit
[`007b7c9`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219682307
Oh, I think MiMa failure is irrelevant to this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user mouendless commented on a diff in the pull request:
https://github.com/apache/spark/pull/13133#discussion_r63500998
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/LocalKMeans.scala ---
@@ -46,17 +46,15 @@ private[mllib] object LocalKMeans extends Loggi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219682529
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219682530
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219682734
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219682710
**[Test build #58686 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58686/consoleFull)**
for PR 12719 at commit
[`d69f521`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219682736
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
1 - 100 of 593 matches
Mail list logo
