Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/11167#issuecomment-183083738
That would be great thanks!! Sorry for the trouble caused by my rushed
merging!
---
If your project is set up for it, you can reply to this email and have your
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183085926
I've updated this to disable the optimizer rule for now (it's still tested
in the LimitPushdownSuite, though).
---
If your project is set up for it, you can reply
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11124#discussion_r52681503
--- Diff: R/pkg/R/mllib.R ---
@@ -126,3 +126,27 @@ setMethod("summary", signature(object =
"PipelineModel"),
return(list(coefficients =
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11174#discussion_r52681432
--- Diff: project/SparkBuild.scala ---
@@ -434,8 +434,11 @@ object Catalyst {
// Generate the parser.
antlr.process
--- End diff
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-18309
**[Test build #51135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51135/consoleFull)**
for PR 11174 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/11124#issuecomment-183092811
@mengxr I am on my way implementing `summary`. The summary of
`stats:kmeans` contains "cluster" "centers" "totss""withinss"
"tot.withinss"
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r52682469
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -21,6 +21,7 @@ import java.util.Collections
import
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9710#issuecomment-183093869
**[Test build #51137 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51137/consoleFull)**
for PR 9710 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183097131
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/10705#issuecomment-183097126
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52684381
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test accuracy.
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52684378
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test accuracy.
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52684369
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -38,8 +45,12 @@ def parseLine(line):
sc =
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52684376
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test accuracy.
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52684370
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test accuracy.
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11132#issuecomment-183099445
@yinxusen Could you help review this PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11142#issuecomment-183098771
@yinxusen Could you help review this PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-183101195
cc @yinxusen
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/11126#issuecomment-183101335
cc @yinxusen
---
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/11142#issuecomment-183100479
@mengxr Don't worry, I'll review all of the replace code PRs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11170#issuecomment-183105465
Sorry I'm still not getting the picture. Can you just paste a screenshot
for the metrics?
---
If your project is set up for it, you can reply to this email and have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11126#issuecomment-183105525
@keypointt @yinxusen Could you start from this PR first and then other
longer ones? @keypointt is new to Spark development. Starting from small ones
could avoid
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-183106640
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/11108#issuecomment-183108594
**[Test build #51145 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51145/consoleFull)**
for PR 11108 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11108#issuecomment-183108603
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/11108#issuecomment-183108605
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/10962#discussion_r52686031
--- Diff: python/pyspark/ml/param/__init__.py ---
@@ -156,9 +156,16 @@ def hasParam(self, paramName):
"""
Tests whether this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11132#issuecomment-183111355
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/11132#issuecomment-183111348
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/9710#issuecomment-183112655
**[Test build #51137 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51137/consoleFull)**
for PR 9710 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11126#issuecomment-183113635
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/11126#issuecomment-183113637
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11044#issuecomment-183114726
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/10975#issuecomment-183116621
Not by design, we just don't have excellent test coverage ...
LGTM. Merged into master. Thanks!
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-183115763
**[Test build #51148 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51148/consoleFull)**
for PR 11109 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183058638
**[Test build #51128 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51128/consoleFull)**
for PR 10705 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11168#issuecomment-183066436
We could add a unit test for this specific case. But I am also looking for
a way to treat these warnings as compile errors; which would be a lot better.
---
If
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10838#issuecomment-183072553
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-183081880
@holdenk I made one pass. I think it is not necessary to verify the links
because the PR author might not be responsible for dead links. Only minor
comments other than
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183084115
**[Test build #51132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51132/consoleFull)**
for PR 10705 at commit
GitHub user sitalkedia opened a pull request:
https://github.com/apache/spark/pull/11175
[SPARK-13279] Remove unnecessary duplicate check in addPendingTask fuâ¦
â¦nction
You can merge this pull request into a Git repository by running:
$ git pull
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/10598#discussion_r52680824
--- Diff: python/pyspark/mllib/classification.py ---
@@ -272,37 +275,42 @@ def train(cls, data, iterations=100, step=1.0,
miniBatchFraction=1.0,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11153#issuecomment-183057571
**[Test build #51124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51124/consoleFull)**
for PR 11153 at commit
Github user redsanket commented on the pull request:
https://github.com/apache/spark/pull/10838#issuecomment-183063914
@zsxwing addressed
---
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/10838#issuecomment-183065836
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/10838#issuecomment-183065989
LGTM. will merge this one once 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11167#issuecomment-183066743
I reverted this since it hasn't passed tests yet.
---
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/11167#issuecomment-183066629
I just merged this but then realized Jenkins hadn't run yet... reverted the
pushed version but will re-merge when Jenkins passes
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10838#issuecomment-183079473
**[Test build #51130 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51130/consoleFull)**
for PR 10838 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/11100#discussion_r52675759
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -216,14 +216,36 @@ class Analyzer(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11140#issuecomment-183088846
**[Test build #51134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51134/consoleFull)**
for PR 11140 at commit
Github user bomeng closed the pull request at:
https://github.com/apache/spark/pull/11086
---
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 bomeng commented on the pull request:
https://github.com/apache/spark/pull/11086#issuecomment-183090608
I did not notice that method and it should work fine for double type. My
question is one absTol may not be enough for all the value types, for example,
float and double
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11157#issuecomment-183056161
**[Test build #51123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51123/consoleFull)**
for PR 11157 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11153#issuecomment-183058007
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/11153#issuecomment-183058010
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/10705#issuecomment-183058138
**[Test build #51128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51128/consoleFull)**
for PR 10705 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11168#issuecomment-183061509
Can we add a unit test for 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11167
---
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/11168#issuecomment-183067115
Yup that's a great idea.
---
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/9893#issuecomment-183069508
**[Test build #51127 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51127/consoleFull)**
for PR 9893 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183069760
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/9893#issuecomment-183069758
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/10838#issuecomment-183071483
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 hvanhovell opened a pull request:
https://github.com/apache/spark/pull/11174
SPARK-13277][BUILD] Follow-up ANTLR warnings are treated as build errors
It is possible to create faulty but legal ANTLR grammars. ANTLR will
produce warnings but also a valid compileable
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11109#discussion_r52675406
--- Diff: dev/lint-python ---
@@ -96,6 +98,32 @@ fi
rm "$PEP8_REPORT_PATH"
+# Check that the documentation builds acceptably, skip check
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11109#discussion_r52675418
--- Diff: python/docs/Makefile ---
@@ -2,7 +2,7 @@
#
# You can set these variables from the command line.
-SPHINXOPTS=
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-18308
You can introduce a warning and see if the build fails as part of this pr.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11109#discussion_r52675400
--- Diff: dev/lint-python ---
@@ -96,6 +98,32 @@ fi
rm "$PEP8_REPORT_PATH"
+# Check that the documentation builds acceptably, skip check
Github user skonto commented on the pull request:
https://github.com/apache/spark/pull/11157#issuecomment-183087696
Need to fix the test. Multiple executors per slave need different handling.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/11175#issuecomment-183087801
Jenkins 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11175#issuecomment-183087708
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-183088637
**[Test build #51133 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51133/consoleFull)**
for PR 11174 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-183088642
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/11174#issuecomment-183088638
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r52681082
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,253 @@
+/*
+ * Licensed to the Apache Software
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r52681156
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -270,19 +260,11 @@ private[spark] class TaskSetManager(
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r52681359
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/BlacklistTrackerSuite.scala ---
@@ -0,0 +1,226 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696689
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696695
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-183144534
**[Test build #51160 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51160/consoleFull)**
for PR 11128 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696683
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696693
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696679
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696690
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/11102#discussion_r52696687
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StratifiedSampling.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-183144622
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/11128#issuecomment-183144619
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/9710#issuecomment-183145517
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9710#issuecomment-183145388
**[Test build #51158 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51158/consoleFull)**
for PR 9710 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9710#issuecomment-183145521
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user movelikeriver commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52697401
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11169#issuecomment-183146209
hm it seems like an important optimization that we wouldn't be able to do
if we cannot skip parsing columns.
---
If your project is set up for it, you can reply to this
Github user movelikeriver commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52697436
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test
Github user movelikeriver commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52697460
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -50,8 +61,17 @@ def parseLine(line):
# Make prediction and test
Github user movelikeriver commented on a diff in the pull request:
https://github.com/apache/spark/pull/11125#discussion_r52697330
--- Diff: examples/src/main/python/mllib/naive_bayes_example.py ---
@@ -38,8 +45,12 @@ def parseLine(line):
sc =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183146095
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-183146086
LGTM if it is creating the proper errors on Jenkins.
---
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/11178#issuecomment-183146096
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11170#issuecomment-183147622
I'm 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 have
401 - 500 of 655 matches
Mail list logo
