Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10747#discussion_r49744149
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/EliminateSerializationSuite.scala
---
@@ -0,0 +1,76 @@
+/*
+ *
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171681629
**[Test build #49401 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49401/consoleFull)**
for PR 10631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171681713
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/10631#issuecomment-171681714
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/10607#issuecomment-171703543
**[Test build #49403 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49403/consoleFull)**
for PR 10607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10607#issuecomment-171717500
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10728
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/5827#issuecomment-171725257
What's different from the one in Spark master now? It would be great to
contribute the parser changes back now we have a full fledged parser in Spark,
and going towards
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10747#discussion_r49761722
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala ---
@@ -0,0 +1,182 @@
+/*
+ * Licensed to the Apache Software
Github user nraychaudhuri commented on a diff in the pull request:
https://github.com/apache/spark/pull/10729#discussion_r49761842
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -109,20 +109,17 @@ private[mesos] trait
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171723257
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10663#discussion_r49760292
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/PoolPage.scala ---
@@ -31,7 +31,7 @@ private[ui] class PoolPage(parent: StagesTab) extends
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10663#discussion_r49760805
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/PoolTable.scala ---
@@ -59,7 +61,8 @@ private[ui] class PoolTable(pools: Seq[Schedulable],
parent:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10755
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10737
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10607#issuecomment-171717280
**[Test build #49403 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49403/consoleFull)**
for PR 10607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10607#issuecomment-171717502
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10728#issuecomment-171720993
Thanks, merging to master, 1.6 and 1.5
---
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10744#issuecomment-171722086
> I'm probably late to the party here, but I thought Akka was simply going
away? does this need to stay around in 2.x?
Yes. This PR removed `actorStream` so
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10701#discussion_r49760002
--- Diff:
core/src/main/scala/org/apache/spark/deploy/mesos/MesosClusterDispatcherArguments.scala
---
@@ -97,6 +102,7 @@ private[mesos] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171722910
**[Test build #49402 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49402/consoleFull)**
for PR 10631 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/10701#issuecomment-171723201
Besides what @skyluc and my comments I think this patch LGTM. Have you
tested this btw?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171723261
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/10701#issuecomment-171723091
jenkins please test
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171725568
Thanks - going to merge this.
---
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 nraychaudhuri commented on the pull request:
https://github.com/apache/spark/pull/10701#issuecomment-171725744
Yes. I have tested this and it seems to work. I will make the necessary
changes
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10596#issuecomment-171568200
**[Test build #49386 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49386/consoleFull)**
for PR 10596 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10755#discussion_r49697139
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -137,45 +137,55 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10596#issuecomment-171568367
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/10596#issuecomment-171568366
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10747#discussion_r49697555
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/EliminateSerializationSuite.scala
---
@@ -0,0 +1,76 @@
+/*
+ * Licensed
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10737#discussion_r49696763
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -137,45 +137,65 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171567878
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10755#discussion_r49696885
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -137,45 +137,55 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171567879
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user grzegorz-chilkiewicz commented on a diff in the pull request:
https://github.com/apache/spark/pull/10741#discussion_r49697177
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/StopWordsRemoverSuite.scala ---
@@ -89,4 +89,22 @@ class StopWordsRemoverSuite
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171570130
**[Test build #49393 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49393/consoleFull)**
for PR 10737 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10735#issuecomment-171570905
**[Test build #49388 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49388/consoleFull)**
for PR 10735 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10735#issuecomment-171571198
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/10755#issuecomment-171567693
**[Test build #49385 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49385/consoleFull)**
for PR 10755 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/10319#issuecomment-171567791
@drcrallen about waiting suggestions, the best way from the scheduler side
is waiting until all tasks are terminated when you like to shutdown. I'm
thinking that if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171567065
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 tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10319#discussion_r49696555
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala
---
@@ -364,7 +380,23 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171567067
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/10735#issuecomment-171571193
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10745#issuecomment-171573197
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10577#issuecomment-171575054
**[Test build #49391 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49391/consoleFull)**
for PR 10577 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171592341
**[Test build #49393 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49393/consoleFull)**
for PR 10737 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171597907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10744#issuecomment-171599618
I'm probably late to the party here, but I thought Akka was simply going
away? does this need to stay around in 2.x?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10745#issuecomment-171613430
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/10745#issuecomment-171613433
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/10577#issuecomment-171575322
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/10604#issuecomment-171575309
**[Test build #49395 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49395/consoleFull)**
for PR 10604 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10577#issuecomment-171575320
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/10737#issuecomment-171592803
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/10737#issuecomment-171592802
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/10604#issuecomment-171597641
**[Test build #49395 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49395/consoleFull)**
for PR 10604 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10663#issuecomment-171610253
**[Test build #49396 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49396/consoleFull)**
for PR 10663 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10729#discussion_r49712068
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -109,20 +109,17 @@ private[mesos] trait
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10745#issuecomment-171613272
**[Test build #49394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49394/consoleFull)**
for PR 10745 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10745#issuecomment-171576641
**[Test build #49394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49394/consoleFull)**
for PR 10745 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10752#issuecomment-171579111
**[Test build #49390 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49390/consoleFull)**
for PR 10752 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10755#discussion_r49700975
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -137,45 +137,55 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10752#issuecomment-171579624
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/10752#issuecomment-171579629
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/10604#issuecomment-171597905
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10756#issuecomment-171597914
As a continuation of https://github.com/apache/spark/pull/8532 it seems OK
to me; I'll wait a minute to see if @mengxr wants to confirm since I haven't
been involved in
Github user yoshidakuy commented on the pull request:
https://github.com/apache/spark/pull/10663#issuecomment-171605226
@JoshRosen @sarutak Sorry for late.
I found same issue in PoolTable, so I fixed it too.
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10714
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171574156
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171580088
LGTM
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10714#issuecomment-171614056
Merged to master, 1.6
---
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/10663#issuecomment-171631873
**[Test build #49396 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49396/consoleFull)**
for PR 10663 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171635825
**[Test build #49399 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49399/consoleFull)**
for PR 10631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171635572
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171637086
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/10631#issuecomment-171637079
**[Test build #49399 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49399/consoleFull)**
for PR 10631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171637085
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/10663#issuecomment-171632053
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/10663#issuecomment-171632055
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/10427#issuecomment-171631018
**[Test build #49397 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49397/consoleFull)**
for PR 10427 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171635576
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/10427#issuecomment-171651804
**[Test build #49397 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49397/consoleFull)**
for PR 10427 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/10668#issuecomment-171658944
No we don't need to wait for that. I actually filed a new jira for what
looks like the same thing.
You have "Totals for 5 Executors" on the top table so how
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171656357
**[Test build #49400 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49400/consoleFull)**
for PR 10631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-171652041
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/10427#issuecomment-171652043
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/10631#issuecomment-171659679
**[Test build #49400 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49400/consoleFull)**
for PR 10631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-171659736
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10663#issuecomment-171838681
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/9710#issuecomment-171838842
**[Test build #49432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49432/consoleFull)**
for PR 9710 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10663#issuecomment-171839437
**[Test build #49433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49433/consoleFull)**
for PR 10663 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10759#issuecomment-171839092
Merged into master 1.6
---
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 adrian-wang opened a pull request:
https://github.com/apache/spark/pull/10762
[SPARK-12828][SQL]add natural join support
Jira:
https://issues.apache.org/jira/browse/SPARK-12828
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10668#issuecomment-171841964
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/10668#issuecomment-171841968
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/10668#issuecomment-171841657
**[Test build #49426 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49426/consoleFull)**
for PR 10668 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10757#issuecomment-171842844
**[Test build #49429 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49429/consoleFull)**
for PR 10757 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10757#issuecomment-171842968
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
1 - 100 of 486 matches
Mail list logo
