Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15242#discussion_r80464688
--- Diff: python/pyspark/sql/streaming.py ---
@@ -315,9 +315,9 @@ def load(self, path=None, format=None, schema=None,
**options):
:param schema:
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15242
[MINOR][PySpark] Fix examples in PySpark documentation
## What changes were proposed in this pull request?
This PR proposes to fix wrongly indented examples in PySpark documentation
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/11601
@hhbyyh seems behavior of approx quantiles may have changed somewhere? Can
you take a look into it?
---
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 issue:
https://github.com/apache/spark/pull/15239
**[Test build #65910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65910/consoleFull)**
for PR 15239 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15241
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 project does not have this
Github user linhnguyen2612 closed the pull request at:
https://github.com/apache/spark/pull/15241
---
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
Github user linhnguyen2612 closed the pull request at:
https://github.com/apache/spark/pull/15241
---
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
GitHub user linhnguyen2612 reopened a pull request:
https://github.com/apache/spark/pull/15241
test
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how
GitHub user linhnguyen2612 opened a pull request:
https://github.com/apache/spark/pull/15241
test
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11601
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65908/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11601
**[Test build #65908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65908/consoleFull)**
for PR 11601 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11601
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65904/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65904/consoleFull)**
for PR 15231 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15240
**[Test build #65909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65909/consoleFull)**
for PR 15240 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65909/
Test FAILed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15239
Huh, it passes in my local and AppVeyor but not in Jenkins. Maybe due to
the R version?
---
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 issue:
https://github.com/apache/spark/pull/15240
**[Test build #65909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65909/consoleFull)**
for PR 15240 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
OK, I just manually fixed and built the docs.
-
[**Original**](https://cloud.githubusercontent.com/assets/6477701/18833109/11098e5c-842a-11e6-9e48-6b3cae7c10b0.png)
-
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65905/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65905/consoleFull)**
for PR 15231 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15239
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65906/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15239
**[Test build #65906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65906/consoleFull)**
for PR 15239 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15239
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65907/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15240
**[Test build #65907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65907/consoleFull)**
for PR 15240 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11601
**[Test build #65908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65908/consoleFull)**
for PR 11601 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15240
**[Test build #65907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65907/consoleFull)**
for PR 15240 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/11601
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 this feature
enabled and
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/11601
Sorry for the delay - been a bit tied up! Overall looks good. Will leave
open a day or two for @sethah or @jkbradley make any final comment.
---
If your project is set up for it, you can reply to
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/15240
[SPARK-17556] Executor side broadcast for broadcast joins
## What changes were proposed in this pull request?
Design doc :
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14035
Thank you for reviewing 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 feature
enabled
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14035
---
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 yanboliang commented on the issue:
https://github.com/apache/spark/pull/14035
LGTM, merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65905/consoleFull)**
for PR 15231 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65904/consoleFull)**
for PR 15231 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15239
**[Test build #65906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65906/consoleFull)**
for PR 15239 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/14035#discussion_r80449593
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/ChiSqSelectorSuite.scala ---
@@ -29,8 +29,7 @@ class ChiSqSelectorSuite extends SparkFunSuite
Github user zhangxinyu1 commented on the issue:
https://github.com/apache/spark/pull/15197
@marmbrus
Thanks for all your sugguestion! I have done the following things:
- Write a short desing on
[JIRA](https://issues.apache.org/jira/browse/SPARK-17631)
- I replace
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15231
The commits I just pushed address the comments except for
https://github.com/apache/spark/pull/15231#discussion_r80417904
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65903/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65903/consoleFull)**
for PR 15168 at commit
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/13599
custom properties file is natively supported by spark, it is user's choice
to use --conf or --properties-file.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/15148#discussion_r80444033
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/lsh/LSH.scala ---
@@ -0,0 +1,290 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user Stibbons commented on the issue:
https://github.com/apache/spark/pull/13599
yes. This file is only written once, dependending the configuration of the
Spark Cluster, and each time you want to send a Python job that will use
virtualenv/conda, user would just add
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/13599
`spark.pyspark.virtualenv.requirements` is mandatory to be required if
virtualenv is enabled (`spark.pyspark.virtualenv.enabled` is true). Otherwise
client will raise exception for now.
And
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65901/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65901/consoleFull)**
for PR 15168 at commit
Github user Stibbons commented on the issue:
https://github.com/apache/spark/pull/13599
I see that everything in this "conf" settings may be set into a .conf file
that define the default values, so user can give to spark-submit with all
default values, I wonder if there is no
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
@mortada Otherwise, let me please try this in my local and post some images
here by myself if you can bear with few days :)
---
If your project is set up for it, you can reply to this email
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
@mortada yes, I understand your point. However, I'd like to avoid change a
lot and I guess @holdenk feels in the same way (she is insightful in Python).
I guess it'd not take a lot of
Github user mortada commented on the issue:
https://github.com/apache/spark/pull/15053
In other words, currently it is not possible for the user to follow the
examples in this docstring below. It's not clear what all these input variables
(`df`, `df2`, etc) are, and where you'd even
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15230
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65900/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15230
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15230
**[Test build #65900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65900/consoleFull)**
for PR 15230 at commit
Github user mortada commented on the issue:
https://github.com/apache/spark/pull/15053
But that's what this PR is supposed to fix, the problem that the docstring
for each individual method is not self-contained :)
I think I now see where I was confused - it seems like we are
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/12696
@srowen Sure, I will wait for a few days and then try to proceed 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65899/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65899 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65899/consoleFull)**
for PR 15168 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/12696
@HyukjinKwon if you want to move this forward and there's no reply, I think
you could fork this and continue it.
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12601
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/12601
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 feature
enabled and wishes so, or
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
@mortada Exactly!
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15196
@sureshthalamati I'm assuming it's required because the existing
`getTableExistsQuery` is overridden in the same way. @JoshRosen if this is what
you had in mind, I'll merge it.
---
If your project
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15236
@lins05 OK, https://github.com/apache/spark/pull/15214 is merged. I don't
think this can relate to https://github.com/apache/spark/pull/15212 because
it's not necessarily going to be added. Is this
Github user mortada commented on the issue:
https://github.com/apache/spark/pull/15053
I see, ok so you mean leave all the docstrings for the individual methods
unchanged, but instead just add
```
"""
>>> df.show()
+-+---+
| name|age|
+-+---+
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15214
---
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 issue:
https://github.com/apache/spark/pull/13599
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65897/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15214
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 feature
enabled and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13599
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13599
**[Test build #65897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65897/consoleFull)**
for PR 13599 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15239
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15239
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65902/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15239
**[Test build #65902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65902/consoleFull)**
for PR 15239 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
Oh, maybe my previous comments were not clear. I meant
https://github.com/apache/spark/blob/master/python/pyspark/sql/dataframe.py#L18
> Also, is the idea that we would define df
Github user mortada commented on the issue:
https://github.com/apache/spark/pull/15053
@HyukjinKwon I may still be confused about something - first of all what do
you mean by the package level docstring? Do you mean here:
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15168#discussion_r80426728
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -499,6 +506,53 @@ case class DescribeTableCommand(table:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65903/consoleFull)**
for PR 15168 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/15231#discussion_r80425776
--- Diff: R/pkg/R/utils.R ---
@@ -698,6 +698,21 @@ isSparkRShell <- function() {
grepl(".*shell\\.R$", Sys.getenv("R_PROFILE_USER"), perl = TRUE)
Github user cjjnjust commented on a diff in the pull request:
https://github.com/apache/spark/pull/15172#discussion_r80425083
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/sasl/aes/SparkAesCipher.java
---
@@ -0,0 +1,270 @@
+/*
+ * Licensed to the
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15239
Let me please cc @felixcheung in case although I know you were in the JIRA.
---
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 cjjnjust commented on a diff in the pull request:
https://github.com/apache/spark/pull/15172#discussion_r80424910
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/sasl/aes/SparkAesCipher.java
---
@@ -0,0 +1,270 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15239
**[Test build #65902 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65902/consoleFull)**
for PR 15239 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15239
[SPARK-17665][SPARKR] Support options/mode all for read/write APIs and
options in other types
## What changes were proposed in this pull request?
This PR includes the changes below:
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15053
Hm.. @mortada It seems the dataframe definition is added into each
docstring. Could you maybe remove the duplicates and then just print the
contents in the package level docstring?
---
If
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15168#discussion_r80424231
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -499,6 +506,53 @@ case class DescribeTableCommand(table:
Github user Stibbons commented on a diff in the pull request:
https://github.com/apache/spark/pull/13599#discussion_r80423208
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -69,6 +84,67 @@ private[spark] class
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15168#discussion_r80422821
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -499,6 +506,53 @@ case class DescribeTableCommand(table:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65901 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65901/consoleFull)**
for PR 15168 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
I addressed those two comments. Thank you for thoughtful review,
@gatorsmile !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15211
**[Test build #65898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65898/consoleFull)**
for PR 15211 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15211
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65898/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15211
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 project does not have this feature
401 - 500 of 536 matches
Mail list logo
