Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318085
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MultiLabelMetricsExample.scala
---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318093
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MultiLabelMetricsExample.scala
---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318144
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/BinaryClassificationMetricsExample.scala
---
@@ -0,0 +1,106 @@
+/*
+ * Licensed
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318073
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MultiLabelMetricsExample.scala
---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318439
--- Diff: examples/src/main/python/mllib/regression_metrics_example.py ---
@@ -0,0 +1,59 @@
+#
+# Licensed to the Apache Software Foundation (ASF)
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9689#discussion_r45318539
--- Diff: examples/src/main/python/mllib/ranking_metrics_example.py ---
@@ -0,0 +1,55 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9832#issuecomment-158007674
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/9832#issuecomment-158007430
**[Test build #46318 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46318/consoleFull)**
for PR 9832 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9057#issuecomment-158013196
@mengxr How do you think about the PMML export for Multinomial Naive Bayes?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158172649
Jenkins, 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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-158173975
@andrewor14 could you help trigger Jenkins? Thanks. I think I don't have
the permission :(
---
If your project is set up for it, you can reply to this email and have
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9797#discussion_r45389631
--- Diff: ec2/spark_ec2.py ---
@@ -591,11 +591,15 @@ def launch_cluster(conn, opts, cluster_name):
# AWS ignores the AMI-specified block
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-158174560
that's odd, you should have permission. 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158174906
**[Test build #46345 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46345/consoleFull)**
for PR 9696 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9825#discussion_r45391437
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkIMain.scala ---
@@ -1221,10 +1221,16 @@ import org.apache.spark.annotation.DeveloperApi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158175789
**[Test build #46345 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46345/consoleFull)**
for PR 9696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158175801
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/9819#issuecomment-158175847
**[Test build #46346 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46346/consoleFull)**
for PR 9819 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158175805
Test FAILed.
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/9775#issuecomment-158176063
this is ok to 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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9825#discussion_r45391606
--- Diff:
repl/scala-2.10/src/test/scala/org/apache/spark/repl/ReplSuite.scala ---
@@ -278,6 +281,27 @@ class ReplSuite extends SparkFunSuite {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9842#issuecomment-158177608
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/9842#issuecomment-158177602
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/9826#issuecomment-158177674
**[Test build #46343 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46343/consoleFull)**
for PR 9826 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9842#issuecomment-158177491
**[Test build #46344 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46344/consoleFull)**
for PR 9842 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158178053
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 the pull request:
https://github.com/apache/spark/pull/9821#issuecomment-158177951
Thanks - merging 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 have this
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9810#discussion_r45392078
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -607,6 +607,89 @@ object ScalaReflection extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158178060
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9810#discussion_r45392361
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -607,6 +607,89 @@ object ScalaReflection extends
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9821
---
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 jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/9824#discussion_r45379122
--- Diff: repl/scala-2.11/src/main/scala/org/apache/spark/repl/Main.scala
---
@@ -43,10 +39,20 @@ object Main extends Logging {
def main(args:
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9831#discussion_r45382352
--- Diff: core/src/test/scala/org/apache/spark/CheckpointSuite.scala ---
@@ -21,17 +21,222 @@ import java.io.File
import scala.reflect.ClassTag
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9722#discussion_r45382273
--- Diff: docs/ml-guide.md ---
@@ -40,6 +40,7 @@ Also, some algorithms have additional capabilities in the
`spark.ml` API; e.g.,
provide class
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9796#discussion_r45384135
--- Diff:
core/src/test/scala/org/apache/spark/deploy/StandaloneDynamicAllocationSuite.scala
---
@@ -395,8 +395,8 @@ class
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-158159573
@andrewor14 yes, I was actually looking for that bug instead of filing a
new one, but couldn't find it. I'll update things.
---
If your project is set up for it, you
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-158159448
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 BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9670#issuecomment-158160419
Thanks for the response @mengxr. I tried setting the following:
`@volatile protected var model: StreamingKMeansModel = new
StreamingKMeansModel(null, null)`
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-158162370
**[Test build #46342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46342/consoleFull)**
for PR 9780 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9288#discussion_r45386808
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -615,7 +615,11 @@ private[spark] class ExecutorAllocationManager(
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-158169482
@maropu any updates? Did you have a chance to do the benchmarks?
---
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/9530#issuecomment-158179685
**[Test build #46349 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46349/consoleFull)**
for PR 9530 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9301#issuecomment-158147997
By the way, maybe this should be changed to 1.6.0 now. Then we need to
backport whatever fix we have here into the 1.5 branch.
---
If your project is set up for it,
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9752#issuecomment-158149585
Yes, @jayv would you mind opening this against the master branch? Then
committers will decide which branches to put in when we merge.
---
If your project is set up
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9831#discussion_r45382443
--- Diff: core/src/test/scala/org/apache/spark/CheckpointSuite.scala ---
@@ -21,17 +21,222 @@ import java.io.File
import scala.reflect.ClassTag
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9833#issuecomment-158153021
Merging 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 your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9841#issuecomment-158158795
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-158158858
@vanzin does this overlap with
https://issues.apache.org/jira/browse/SPARK-4134?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9841#issuecomment-158158799
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9836#discussion_r45384357
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/IsotonicRegression.scala ---
@@ -240,4 +254,61 @@ class IsotonicRegressionModel private[ml] (
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9819#issuecomment-158166159
**[Test build #46338 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46338/consoleFull)**
for PR 9819 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9819#issuecomment-158166443
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/9819#issuecomment-158166439
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 thunterdb commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158169615
@mengxr with the fixes, the top menu breaks before the side menu :-)
![screen shot 2015-11-19 at 11 30 13
Github user thunterdb commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158169959
This is about as much as I can do with my very limited knowledge of CSS, so
additional fixes can be done in a separate PR.
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158172384
**[Test build #46343 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46343/consoleFull)**
for PR 9826 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9831#issuecomment-158153906
Looks fine. Just make the tests pass.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-158161862
> if we call (1) after this line, it will release memory for other unrolled
failed block. if we call (2), we can't got the specific memory for that
MEMORY_AND_DISK
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9842#issuecomment-158172157
**[Test build #46344 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46344/consoleFull)**
for PR 9842 at commit
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9722#discussion_r45381957
--- Diff: docs/ml-clustering.md ---
@@ -0,0 +1,31 @@
+---
+layout: global
+title: Clustering - ML
+displayTitle: ML - Clustering
+---
Github user thunterdb commented on a diff in the pull request:
https://github.com/apache/spark/pull/9826#discussion_r45381998
--- Diff: docs/_includes/nav-left-wrapper-ml.html ---
@@ -0,0 +1,6 @@
+
+ML
--- End diff --
sure
---
If your project is set up
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9722#discussion_r45382669
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaLDAExample.java ---
@@ -0,0 +1,97 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9831#discussion_r45382804
--- Diff: core/src/test/scala/org/apache/spark/CheckpointSuite.scala ---
@@ -21,17 +21,222 @@ import java.io.File
import scala.reflect.ClassTag
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/9722#issuecomment-158153601
LGTM after changes
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9831#discussion_r45382679
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/rdd/TrackStateRDDSuite.scala
---
@@ -278,6 +287,50 @@ class TrackStateRDDSuite extends
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9836#discussion_r45384012
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/IsotonicRegression.scala ---
@@ -240,4 +254,61 @@ class IsotonicRegressionModel private[ml] (
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9828#issuecomment-158158186
OK. I am merging it to master and branch 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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9288#issuecomment-158168054
@XuTingjun A more robust way to do this may be to keep track of
```
private val stageIdToRunningTaskIds = new mutable.HashMap[Int,
mutable.HashSet[Int]]
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/9842
[SPARK-11858][SQL] Move sql.columnar into sql.execution.
In addition, tightened visibility of a lot of classes in the columnar
package from private[sql] to private[columnar].
You can merge this pull
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-158172457
I still don't see why it's necessary to change the class path of the
client. If you're using Spark with HBase you should change the driver /
executor classpaths, not
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9841#issuecomment-158152446
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
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9722#discussion_r45382120
--- Diff: docs/ml-clustering.md ---
@@ -0,0 +1,31 @@
+---
+layout: global
+title: Clustering - ML
+displayTitle: ML - Clustering
+---
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9837#issuecomment-158154158
@woj-i please open the patch against the master branch instead. Committers
will backport it into branch-1.5 when they merge it.
---
If your project is set up for
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9837#issuecomment-158154058
@tgravescs @harishreedharan
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9796#issuecomment-158156689
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9841#issuecomment-158159773
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 dskrvk commented on the pull request:
https://github.com/apache/spark/pull/9696#issuecomment-158163207
Jenkins, 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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9838#discussion_r45396273
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -432,9 +432,9 @@ class Word2Vec extends Serializable with Logging {
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9588#issuecomment-158190433
This kind of discussion should happen on JIRA. Briefly, temporary tables
are just pointers to a logical plan (similar to a view that is temporary to the
session).
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-158191955
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9762
---
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/9773
---
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/9780#issuecomment-158199248
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/9849#issuecomment-158234543
**[Test build #46371 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46371/consoleFull)**
for PR 9849 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9836#issuecomment-158235753
**[Test build #46370 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46370/consoleFull)**
for PR 9836 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-158237731
Should we do this in `SparkContext` as well?
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9419#issuecomment-158237648
Thank you everyone!
---
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/9850#issuecomment-158237775
[Test build #46372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46372/consoleFull)
for PR 9850 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/9769#discussion_r45419720
--- Diff: R/pkg/R/DataFrame.R ---
@@ -717,25 +717,30 @@ setMethod("collect",
# data of complex type can be held. But getting a cell
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-158238466
**[Test build #46355 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46355/consoleFull)**
for PR 9780 at commit
GitHub user tedyu opened a pull request:
https://github.com/apache/spark/pull/9852
Prevent the call to SparkContext#stop() in the listener bus's thread
This is continuation of SPARK-11761
Andrew suggested adding this protection. See tail of
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9849#issuecomment-158242082
**[Test build #46371 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46371/consoleFull)**
for PR 9849 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9849#issuecomment-158242191
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/9849#issuecomment-158242190
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/9836#issuecomment-158243929
**[Test build #46370 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46370/consoleFull)**
for PR 9836 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9836#issuecomment-158244036
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/9831#issuecomment-158243888
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/9831#issuecomment-158243889
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/9846#issuecomment-158244525
**[Test build #46358 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46358/consoleFull)**
for PR 9846 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9846#issuecomment-158244665
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
101 - 200 of 699 matches
Mail list logo