Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140568143
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/7884#issuecomment-140568144
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/7884#issuecomment-140568085
[Test build #42501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42501/console)
for PR 7884 at commit
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8671#discussion_r39575837
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -202,55 +207,86 @@ private[spark] class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7884
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-140575395
Merged build triggered.
---
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 sryza commented on the pull request:
https://github.com/apache/spark/pull/7918#issuecomment-140575553
Ah, yeah, it does look like ReflectionUtils.newInstance caches the
constructor. In that case I'd be OK with removing the input format cache
entirely. Any thoughts
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8761#issuecomment-140575460
Merged build started.
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39578088
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39579218
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39579338
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39582053
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39582006
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8740#issuecomment-140587947
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8740#issuecomment-140587966
Merged build started.
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39583944
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnExtensionService.scala
---
@@ -0,0 +1,198 @@
+/*
+ * Licensed to the Apache
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39583869
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140593623
[Test build #1761 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1761/console)
for PR 8764 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8769#issuecomment-140593845
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8769#issuecomment-140593857
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-140614860
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-140614869
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-140614859
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-140614868
Merged build started.
---
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/8561#issuecomment-140569092
[Test build #42508 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42508/consoleFull)
for PR 8561 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39577138
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnEventListener.scala
---
@@ -0,0 +1,142 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39577849
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8676#issuecomment-140578273
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/8775#issuecomment-140578509
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39577927
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-140578506
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/8775#issuecomment-140578481
[Test build #42511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42511/console)
for PR 8775 at commit
Github user piaozhexiu commented on the pull request:
https://github.com/apache/spark/pull/8512#issuecomment-140580241
@yhuai @liancheng thank you very much for reviewing! I'll update my PR to
incorporate your comments soon.
To answer your questions-
> I am trying to
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39579779
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39579818
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140581751
[Test build #1762 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1762/consoleFull)
for PR 8764 at commit
Github user yjshen commented on the pull request:
https://github.com/apache/spark/pull/8200#issuecomment-140610959
@marmbrus converting a filter into CNF may lead to an expanded filter,
which I think is not necessarily a general optimisation.
---
If your project is set up for it,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8777#discussion_r39589775
--- Diff: python/pyspark/sql/functions.py ---
@@ -189,6 +190,14 @@ def approxCountDistinct(col, rsd=None):
return Column(jc)
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8777#discussion_r39589771
--- Diff: python/pyspark/sql/functions.py ---
@@ -189,6 +190,14 @@ def approxCountDistinct(col, rsd=None):
return Column(jc)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-140613869
Merged build started.
---
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 ericl commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-140614349
@mengxr I did the refactoring as suggested
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-140615136
[Test build #42523 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42523/consoleFull)
for PR 8718 at commit
Github user GavinGavinNo1 commented on the pull request:
https://github.com/apache/spark/pull/8713#issuecomment-140621464
@marmbrus Sorry to disturb again. Could you please give me a reply? It's my
first try. Maybe I need some advice.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-140630773
[Test build #42523 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42523/console)
for PR 8718 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8512#discussion_r39574274
--- Diff: core/src/main/scala/org/apache/spark/rdd/UnionRDD.scala ---
@@ -62,6 +64,14 @@ class UnionRDD[T: ClassTag](
var rdds: Seq[RDD[T]])
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140565690
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/7884#issuecomment-140565459
[Test build #42502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42502/console)
for PR 7884 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-140568921
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-140568936
Merged build started.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-140574389
Re-posting previous PR with a fix for the issue that caused tests to fail
in other PRs. For the changes since the last PR, see only the second commit.
I'm not
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39577223
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-140579762
Merged build triggered.
---
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 Jianfeng-chs closed the pull request at:
https://github.com/apache/spark/pull/8770
---
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
Github user Jianfeng-chs commented on the pull request:
https://github.com/apache/spark/pull/8770#issuecomment-140579799
um, let me close this one to submit a new one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-140579782
Merged build started.
---
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 mccheah commented on the pull request:
https://github.com/apache/spark/pull/8763#issuecomment-140579651
Jenkins, test 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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39579943
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140581881
[Test build #1763 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1763/consoleFull)
for PR 8764 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140581910
[Test build #1761 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1761/consoleFull)
for PR 8764 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39581283
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39581185
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryService.scala
---
@@ -0,0 +1,981 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39582809
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnTimelineUtils.scala
---
@@ -0,0 +1,720 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39582719
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnTimelineUtils.scala
---
@@ -0,0 +1,720 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140588247
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/8764#issuecomment-140588146
[Test build #42510 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42510/console)
for PR 8764 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39584306
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnClusterSchedulerBackend.scala
---
@@ -37,9 +38,12 @@ private[spark] class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r39584199
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnExtensionService.scala
---
@@ -0,0 +1,198 @@
+/*
+ * Licensed to the Apache
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8744#issuecomment-140590346
I kinda reviewed half of this; it's still a pretty large change. The
services stuff could be ripped off and reviewed separately, too.
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8740#issuecomment-140592702
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/8740#issuecomment-140592701
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/8776#issuecomment-140601943
[Test build #42521 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42521/console)
for PR 8776 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-140601612
Ok, I think I see what the problem is. But your fix is not correct.
The problem is here:
doRequestTotalExecutors(
numExistingExecutors
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8776#issuecomment-140602320
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user Jianfeng-chs opened a pull request:
https://github.com/apache/spark/pull/8777
[SPARK-10577] [PySpark] DataFrame hint for broadcast join
https://issues.apache.org/jira/browse/SPARK-10577
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8676
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8752#issuecomment-140608613
Merged into master. 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 project does not have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8752
---
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 pallavipr commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-140619445
Looks good Rama. We are almost done with DB2 changes - will send for review
soon.
One question, did you introduce a stringDataType property in connection
Github user XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/7918#issuecomment-140619178
@JoshRosen, Can you have a look on this? 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
Github user lkhamsurenl commented on the pull request:
https://github.com/apache/spark/pull/8609#issuecomment-140621230
Sorry for the late response! I see what you're saying. The difficulty with
that approach I am having is in inside def binSeqOp(agg:
Array[DTStatsAggregator],
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140621207
[Test build #42525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42525/consoleFull)
for PR 8682 at commit
Github user abraithwaite commented on the pull request:
https://github.com/apache/spark/pull/2573#issuecomment-140622568
Hello!
I was reading the explanation and I'm not quite sure I understand the
reasoning still. I spent a bit too long trying to figure out how to configure
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140619998
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140624142
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/8682#issuecomment-140624097
[Test build #42525 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42525/console)
for PR 8682 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140624143
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/6457#issuecomment-140620297
[Test build #42517 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42517/console)
for PR 6457 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140619959
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6457#issuecomment-140620519
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/6457#issuecomment-140620517
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 viesti commented on the pull request:
https://github.com/apache/spark/pull/8349#issuecomment-140625049
@tnachen Thanks for the kind advice! :) I'll have a try, although we found
out that AWS EMR seems to support running Spark also and got an initial hello
world PySpark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-140631028
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/8718#issuecomment-140631024
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/8512#issuecomment-140567731
It will be great if we can have more comments to explain `SparkS3Util`,
specially those private methods. So, a developer who can quickly understand the
flow and methods
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-140567796
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140569892
Merged build started.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140569774
Merged into master. 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 project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8764#issuecomment-140569830
Merged build triggered.
---
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/8775#issuecomment-140576337
[Test build #42511 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42511/consoleFull)
for PR 8775 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-140578069
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
1 - 100 of 747 matches
Mail list logo
