Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11336#issuecomment-188198217
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user vectorijk commented on a diff in the pull request:
https://github.com/apache/spark/pull/11321#discussion_r53924161
--- Diff: python/pyspark/mllib/fpm.py ---
@@ -40,6 +41,11 @@ class FPGrowthModel(JavaModelWrapper):
>>> model = FPGrowth.train(rdd, 0.6, 2)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188198030
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/11000#issuecomment-188197909
**[Test build #51873 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51873/consoleFull)**
for PR 11000 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11255#issuecomment-188225305
Merged to master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188267302
**[Test build #51876 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51876/consoleFull)**
for PR 11345 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188198033
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/11336#issuecomment-188198023
**[Test build #51863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51863/consoleFull)**
for PR 11336 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11321#issuecomment-188216513
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/11321#issuecomment-188216220
**[Test build #51874 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51874/consoleFull)**
for PR 11321 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188229315
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/11324#issuecomment-188229075
**[Test build #51872 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51872/consoleFull)**
for PR 11324 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11347#issuecomment-188276819
**[Test build #51878 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51878/consoleFull)**
for PR 11347 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11344#issuecomment-188195141
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/11344#issuecomment-188195143
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11334#issuecomment-188202428
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 oliverpierson commented on a diff in the pull request:
https://github.com/apache/spark/pull/11319#discussion_r53934003
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/QuantileDiscretizer.scala ---
@@ -103,6 +103,13 @@ final class QuantileDiscretizer(override
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/11345
[SPARK-13472][SparkR] Fix unstable Kmeans test in R
JIRA: https://issues.apache.org/jira/browse/SPARK-13472
## What changes were proposed in this pull request?
One Kmeans test in R
Github user cloud-fan closed the pull request at:
https://github.com/apache/spark/pull/7
---
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/11347#issuecomment-188277420
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/11347#issuecomment-188277423
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/11347#issuecomment-188277413
**[Test build #51878 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51878/consoleFull)**
for PR 11347 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188212965
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/11260#issuecomment-188212970
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11319#discussion_r53937600
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/QuantileDiscretizer.scala ---
@@ -103,6 +103,13 @@ final class QuantileDiscretizer(override val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188275234
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/11345#issuecomment-188275009
**[Test build #51876 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51876/consoleFull)**
for PR 11345 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11336#issuecomment-188198216
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/11324#issuecomment-188229317
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188233729
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188245765
**[Test build #51875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51875/consoleFull)**
for PR 11324 at commit
Github user oliverpierson commented on a diff in the pull request:
https://github.com/apache/spark/pull/11319#discussion_r53936527
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/QuantileDiscretizer.scala ---
@@ -103,6 +103,13 @@ final class QuantileDiscretizer(override
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188217429
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11255
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188257864
It is weird. Some other PRs like #11344 (just document change) also failed
at this SparkR unit tests.
---
If your project is set up for it, you can reply to this email
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188262295
cc @mengxr This test failed in #10939, #11344 and #11260. Please see if
this fix is appropriate. Thanks.
---
If your project is set up for it, you can reply to this
GitHub user steveloughran opened a pull request:
https://github.com/apache/spark/pull/11346
[SPARK-13471] [SQL]: WiP update hive version to 1.2.1.1.spark
## What changes were proposed in this pull request?
This updates the hive dependency from 1.2.1.spark to 1.2.1.1.spark,
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11344#issuecomment-188213659
@srowen Some ScalaDoc will end with two dots if we don't fix, you can refer
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188217276
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11321#issuecomment-188216522
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188216762
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 yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11000#issuecomment-188217094
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188224913
**[Test build #51867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51867/consoleFull)**
for PR 11324 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/11347
[SPARK-13233][SQL][WIP] Python Dataset (basic version)
## What changes were proposed in this pull request?
This PR introduce a new API: Python dataset. Conceptually it's a
combination
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11342#issuecomment-188274034
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188275244
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/11321#issuecomment-188209489
**[Test build #51874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51874/consoleFull)**
for PR 11321 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/11249#discussion_r53925855
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/Checkpoint.scala ---
@@ -41,6 +41,13 @@ class Checkpoint(ssc: StreamingContext, val
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/11336#issuecomment-188214706
The R version used by Jenkins seems to be 3.2.x (can't remember clearly).
There is a JIRA requesting using R 3.1.1,
https://issues.apache.org/jira/browse/SPARK-11255,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188225161
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/11324#issuecomment-188225166
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11334#issuecomment-188257500
Merged to 1.6
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188262253
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188262375
@srowen 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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11347#discussion_r53944846
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/python.scala
---
@@ -0,0 +1,34 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11342#issuecomment-188276579
**[Test build #51879 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51879/consoleFull)**
for PR 11342 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10939#issuecomment-188197293
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/10939#issuecomment-188197289
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/10939#issuecomment-188197186
**[Test build #51869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51869/consoleFull)**
for PR 10939 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11337#discussion_r53923847
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -537,9 +537,14 @@ private[spark] class Client(
Github user thomastechs commented on the pull request:
https://github.com/apache/spark/pull/11306#issuecomment-188207119
@yhaui @SparkQA Looks like the build failed due to some other unit test
cases, not related to this PR
Could you please confirm?
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188212474
**[Test build #51868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51868/consoleFull)**
for PR 11260 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188297160
retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11324#issuecomment-188319168
**[Test build #51875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51875/consoleFull)**
for PR 11324 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11346#issuecomment-188278940
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/11346#issuecomment-188278935
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11345
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188292453
@srowen If this is ok, can you merge this since it is a hotfix. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188294778
Merged into master. Thanks for the quick fix!
---
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/11260#issuecomment-188302330
**[Test build #51882 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51882/consoleFull)**
for PR 11260 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11347#issuecomment-188284926
**[Test build #51880 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51880/consoleFull)**
for PR 11347 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11344#issuecomment-188281271
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/11345#issuecomment-188296958
@mengxr 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/11344#issuecomment-188308843
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/11324#issuecomment-188319641
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/11347#issuecomment-188285763
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/11347#issuecomment-188285751
**[Test build #51880 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51880/consoleFull)**
for PR 11347 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11347#issuecomment-188285760
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/11324#issuecomment-188319652
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/11344#issuecomment-188290020
**[Test build #51881 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51881/consoleFull)**
for PR 11344 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11344#issuecomment-188308748
**[Test build #51881 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51881/consoleFull)**
for PR 11344 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11344#issuecomment-188308845
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/11277#issuecomment-188387223
@andrewor14 This is so that users can be able to set java properties when
running the mesos cluster dispatcher, it's really useful for testing the
dispatcher
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11141#issuecomment-188398613
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/11349#issuecomment-188401436
This PR is just for branch 1.6. Master does not have this problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11141#issuecomment-188401367
**[Test build #51887 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51887/consoleFull)**
for PR 11141 at commit
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/11349
[SPARK-13454] [SQL] Allow users to drop a table with a name starting with
an underscore.
## What changes were proposed in this pull request?
This change adds a workaround to allow users to
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/11136#discussion_r53911268
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/GeneralizedLinearRegressionSuite.scala
---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188155538
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/11136#discussion_r53911596
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -0,0 +1,565 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188155198
**[Test build #51858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51858/consoleFull)**
for PR 11260 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188155543
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/9483#issuecomment-188155365
**[Test build #51861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51861/consoleFull)**
for PR 9483 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9483#issuecomment-188155757
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/9483#issuecomment-188155753
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/11260#issuecomment-188170993
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11322#issuecomment-188171986
The code looks OK... I think two passes is too much complexity.
I guess the thing is that I've never seen log error used before. That could
just be my
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11342#issuecomment-188173962
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/11342#issuecomment-188173956
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 yanboliang opened a pull request:
https://github.com/apache/spark/pull/11344
[] [] [] Clean up sharedParams
## What changes were proposed in this pull request?
Remove duplicated dot at the end of some sharedParams in ScalaDoc.
cc @mengxr @srowen
## How was
1 - 100 of 581 matches
Mail list logo
