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
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):
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
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 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
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
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
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):
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):
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
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
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 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
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
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
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
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 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
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
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):
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
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
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
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
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
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
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")
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
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
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 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
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
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
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
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
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 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 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()
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
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
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(
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 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
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
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):
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 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
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
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13146#issuecomment-219690542
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13146#issuecomment-219690545
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219700590
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219706864
**[Test build #58691 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58691/consoleFull)**
for PR 12627 at commit
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
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
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):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219684430
**[Test build #58684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58684/consoleFull)**
for PR 13148 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219684101
**[Test build #58687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58687/consoleFull)**
for PR 12719 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13149#issuecomment-219691730
**[Test build #58688 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58688/consoleFull)**
for PR 13149 at commit
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
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):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219684646
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13148#issuecomment-219684645
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219687641
Thank you for review, @srowen .
Probably, there exists similar cases in other modules, too.
But, for the other module, I guess the patterns are simple
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-219690860
Hi, All.
I'm reporting about the recent failures of Travis CI here.
Since this PR was committed a week ago, I've been monitoring Travis CI on
my
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13149#issuecomment-219698992
**[Test build #58688 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58688/consoleFull)**
for PR 13149 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13149#issuecomment-219699102
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
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219708181
Why is that `Alias` not analyzed? Isn't
`FormatNumber(Literal(4.asInstanceOf[Byte]), Literal(3))` a resolved expression?
---
If your project is set up for it, you
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 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
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
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):
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/13149
[SPARK-15362] [ML] Make spark.ml KMeansModel load backwards compatible
## What changes were proposed in this pull request?
[SPARK-14646](https://issues.apache.org/jira/browse/SPARK-14646)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13147#issuecomment-219692871
**[Test build #58683 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58683/consoleFull)**
for PR 13147 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13147#issuecomment-219693076
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-219697407
**[Test build #58689 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58689/consoleFull)**
for PR 11996 at commit
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219683326
Hmm. @cloud-fan .
Unfortunately, for `resolved`, we can not pass the tests without that.
For example, `StringExpressionsSuite.format_number` has the
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219683646
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 user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13147#issuecomment-219693080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219700589
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13146#issuecomment-219700414
**[Test build #58690 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58690/consoleFull)**
for PR 13146 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219706637
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 this
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219688169
At this time, MiMa test passed. Let's wait and see the result.
By the way, please note that I only replaced `transformAllExpressions` in
this final commit.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13146#issuecomment-219690423
**[Test build #58681 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58681/consoleFull)**
for PR 13146 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13149#issuecomment-219699106
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-219698138
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-219698135
**[Test build #58689 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58689/consoleFull)**
for PR 11996 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-219698137
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219700387
**[Test build #58687 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58687/consoleFull)**
for PR 12719 at commit
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
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):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219691146
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219690994
**[Test build #58682 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58682/consoleFull)**
for PR 12627 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219691144
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
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12627#issuecomment-219715832
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 this
101 - 200 of 586 matches
Mail list logo
