Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-143981017
Originally, we implemented a "sortDF" function in SparkR DataFrame
corresponds to the "sort" function of the Scala DataFrame. Later, "sortDF" was
renamed to "arrange"
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8933#issuecomment-143982856
cc @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 this
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8920#discussion_r40646379
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1848,3 +1848,78 @@ setMethod("crosstab",
sct <- callJMethod(statFunctions, "crosstab", col1, col2)
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8920#discussion_r40645685
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1848,3 +1848,78 @@ setMethod("crosstab",
sct <- callJMethod(statFunctions, "crosstab", col1, col2)
Github user NarineK commented on a diff in the pull request:
https://github.com/apache/spark/pull/8920#discussion_r40639413
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1848,3 +1848,67 @@ setMethod("crosstab",
sct <- callJMethod(statFunctions, "crosstab", col1, col2)
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8869#discussion_r40639291
--- Diff: R/pkg/R/DataFrameStatFunctions.R ---
@@ -0,0 +1,102 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+#
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8920#discussion_r40645086
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1848,3 +1848,78 @@ setMethod("crosstab",
sct <- callJMethod(statFunctions, "crosstab", col1, col2)
GitHub user taishi-oss opened a pull request:
https://github.com/apache/spark/pull/8935
[SPARK-10263] [ML] Add @Since annotation to ml.param and ml.*
Add Since annotations to ml.param and ml.*
You can merge this pull request into a Git repository by running:
$ git pull
Github user travishegner commented on the pull request:
https://github.com/apache/spark/pull/8780#issuecomment-144054401
So any thoughts on 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
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/8938
[SPARK-10851][SPARKR] Exception not failing R applications (in yarn cluster
mode)
You can merge this pull request into a Git repository by running:
$ git pull
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/8936#issuecomment-144007103
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-144015558
[Test build #1824 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1824/console)
for PR 8881 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/8937
[SPARK-10736] [ML] Use 1 for all ratings if $(ratingCol) = ""
For some implicit dataset, ratings may not exist in the training data. In
this case, we can assume all observed pairs to be positive
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-144035049
@marmbrus How do you think this fix? As the issue priority is very high, I
think we better fix it ASAP.
---
If your project is set up for it, you can reply to
Github user vectorijk commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143988921
@mengxr @GayathriMurali Thanks so so much for code review!
I cleaned up the code~
---
If your project is set up for it, you can reply to this email and have your
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/8866#issuecomment-144023820
@jkbradley
---
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 yanboliang opened a pull request:
https://github.com/apache/spark/pull/8936
[SPARK-10490] [ML] Consolidate the Cholesky solvers in WeightedLeastSquares
and ALS
Consolidate the Cholesky solvers in WeightedLeastSquares and ALS.
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-144015277
[Test build #1824 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1824/consoleFull)
for PR 8881 at commit
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/8867#discussion_r40679882
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ExecutorDelegationTokenUpdater.scala
---
@@ -76,7 +76,10 @@ private[spark] class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/8867#discussion_r40680554
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -544,6 +545,7 @@ private[spark] class Client(
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8744#issuecomment-144080509
Sorry I haven't had time to follow all of these changes, which version of
ATS are you testing this on and at what scale? I'm assuming ATS v1 since v2
still in
GitHub user ryan-williams opened a pull request:
https://github.com/apache/spark/pull/8939
[SPARK-10871] include number of executor failures in error msg
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ryan-williams/spark errmsg
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-144101875
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/8908#issuecomment-144101883
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/8933#issuecomment-144101846
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/8374#issuecomment-144101939
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/8926#issuecomment-144103870
[Test build #43083 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43083/consoleFull)
for PR 8926 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8934#issuecomment-144103835
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/8374#issuecomment-144104374
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 NarineK commented on the pull request:
https://github.com/apache/spark/pull/8924#issuecomment-144109055
closing because it's a duplicate
---
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/6848#issuecomment-144109858
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user NarineK closed the pull request at:
https://github.com/apache/spark/pull/8924
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8938#issuecomment-144109380
Thanks @sun-rui for the PR. I didn't follow the problem report very closely
-- Could you explain the fix in the PR description for it to be available in
the future ?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8908#issuecomment-144110238
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/8931#issuecomment-144111611
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/8934#issuecomment-144112736
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/8937#issuecomment-144118294
[Test build #43078 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43078/console)
for PR 8937 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8362#issuecomment-144118463
@hvanhovell @rxin Just realized that the tungsten aggregation does not
support var-length types in aggregation buffer, so we can't have sparse version
without
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8926#discussion_r40698000
--- Diff: python/pyspark/ml/regression.py ---
@@ -609,6 +611,147 @@ class GBTRegressionModel(TreeEnsembleModels):
"""
+@inherit_doc
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8926#discussion_r40697984
--- Diff: python/pyspark/ml/regression.py ---
@@ -609,6 +611,147 @@ class GBTRegressionModel(TreeEnsembleModels):
"""
+@inherit_doc
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8935#issuecomment-144101800
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8938#issuecomment-144101778
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/8908#issuecomment-144101927
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/8936#issuecomment-144101832
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/8938#issuecomment-144101804
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/6848#issuecomment-144101992
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/8939#issuecomment-144101764
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/7052#issuecomment-144101980
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/8934#issuecomment-144101807
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/8505#issuecomment-144101954
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/8920#issuecomment-144103039
[Test build #43085 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43085/console)
for PR 8920 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-144102630
[Test build #43093 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43093/consoleFull)
for PR 7052 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8934#issuecomment-144101851
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/8908#issuecomment-144102890
[Test build #43086 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43086/consoleFull)
for PR 8908 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8934#issuecomment-144103683
[Test build #43080 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43080/consoleFull)
for PR 8934 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8933#issuecomment-144103816
[Test build #43081 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43081/consoleFull)
for PR 8933 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-144103804
[Test build #43089 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43089/consoleFull)
for PR 8374 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-144103038
[Test build #43082 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43082/consoleFull)
for PR 8931 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/8358#issuecomment-144107346
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8864#issuecomment-144109691
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/8908#issuecomment-144110099
[Test build #43086 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43086/console)
for PR 8908 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8936#issuecomment-144117850
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/8934#issuecomment-144112765
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/8937#issuecomment-144118490
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/8934#issuecomment-144119798
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/8937#issuecomment-144118488
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8926#discussion_r40698242
--- Diff: python/pyspark/ml/regression.py ---
@@ -609,6 +611,147 @@ class GBTRegressionModel(TreeEnsembleModels):
"""
+@inherit_doc
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-144122575
LGTM except some minor inline comments
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7786#issuecomment-144101993
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/7417#issuecomment-144101968
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/8939#issuecomment-144101794
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/7786#issuecomment-144101960
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/8505#issuecomment-144102210
[Test build #43088 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43088/consoleFull)
for PR 8505 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8933#issuecomment-144101816
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/8936#issuecomment-144101792
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/7786#issuecomment-144103185
[Test build #43091 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43091/consoleFull)
for PR 7786 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-144101849
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/8931#issuecomment-144101834
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/8864#issuecomment-144103408
[Test build #43087 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43087/consoleFull)
for PR 8864 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7417#issuecomment-144102643
[Test build #43092 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43092/consoleFull)
for PR 7417 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144101956
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/8864#issuecomment-144101938
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 asokadiggs commented on the pull request:
https://github.com/apache/spark/pull/8930#issuecomment-144106274
Correct - there is no separate declaration for drop_duplicates. There is a
section in dataframe.py at approximately line 1280-1285 that sets
drop_duplicates =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8937#issuecomment-144103891
[Test build #43078 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43078/consoleFull)
for PR 8937 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-144107798
[Test build #43090 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43090/console)
for PR 8323 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8864#issuecomment-144109499
[Test build #43087 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43087/console)
for PR 8864 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-144101872
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/8926#issuecomment-144110823
[Test build #43083 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43083/console)
for PR 8926 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8864#issuecomment-144109689
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/6848#issuecomment-144102816
[Test build #43094 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43094/consoleFull)
for PR 6848 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8908#issuecomment-144110234
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/8926#issuecomment-144111040
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/8505#issuecomment-144116560
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/6848#issuecomment-144109742
[Test build #43094 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43094/console)
for PR 6848 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-144111542
[Test build #43082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43082/console)
for PR 8931 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8936#issuecomment-144117676
[Test build #43079 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43079/console)
for PR 8936 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8505#issuecomment-144116109
[Test build #43088 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43088/console)
for PR 8505 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8937#discussion_r40697270
--- Diff: mllib/src/main/scala/org/apache/spark/ml/recommendation/ALS.scala
---
@@ -315,12 +315,17 @@ class ALS(override val uid: String) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8505#issuecomment-144101926
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/8374#issuecomment-144101969
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
1 - 100 of 435 matches
Mail list logo
