Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
okay, I'll try to fix in that way, 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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16263#discussion_r92337930
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -400,10 +402,19 @@ def toLocalIterator(self):
>>> list(df.toLocalIterator())
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16142
cc @vanzin
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16274
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/16274
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70123/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16274
**[Test build #70123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70123/consoleFull)**
for PR 16274 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16266
@srowen, I think it is ready for a second look.
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/16277
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 and wishes so, or if the
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r92335449
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -56,33 +58,93 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70122/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
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/14079
**[Test build #70122 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70122/consoleFull)**
for PR 14079 at commit
Github user vijoshi commented on a diff in the pull request:
https://github.com/apache/spark/pull/16119#discussion_r92333556
--- Diff: python/pyspark/sql/context.py ---
@@ -72,8 +72,13 @@ def __init__(self, sparkContext, sparkSession=None,
jsqlContext=None):
self._sc
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16030
After an offline discussion with @liancheng , here is the result:
**Why does the test fail?**
1. We write a parquet file with schema `[a: long, b: int]` to path
`/data/a=1`.
2.
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/16263#discussion_r92332668
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -400,10 +402,19 @@ def toLocalIterator(self):
>>> list(df.toLocalIterator())
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16194
Good point. This make me think of the usage of `instr.logParams(params:
_*)` in training instrumentation [https://github.com/apache/spark/pull/15671].
IMIO, params are copied from its
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16277
**[Test build #70125 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70125/consoleFull)**
for PR 16277 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16277#discussion_r92331760
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -557,9 +562,10 @@ abstract class TreeNode[BaseType <:
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16277#discussion_r92331508
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -534,19 +539,16 @@ abstract class TreeNode[BaseType <:
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16277
cc @yhuai @liancheng @davies
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/16277
[SPARK-18854][SQL] numberedTreeString and apply(i) inconsistent for
subqueries
## What changes were proposed in this pull request?
This is a bug introduced by subquery handling.
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15018#discussion_r92331409
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/IsotonicRegression.scala
---
@@ -344,27 +344,30 @@ class IsotonicRegression private
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16266
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/16266
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70121/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16266
**[Test build #70121 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70121/consoleFull)**
for PR 16266 at commit
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/16030
@maropu @brkyvz Sorry for the delay, I was blocked by some other tasks
during the last a few days.
@cloud-fan and I just did some investigation and we think we came up with a
minimal fix
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
Sorry for the last minute comment. I did not realize it until I manually
run these test cases in Hive.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15717#discussion_r92329696
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -877,6 +877,35 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15717#discussion_r92329570
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -877,6 +877,35 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16273
**[Test build #70124 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70124/consoleFull)**
for PR 16273 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16273
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 wishes so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
Yeah, let me update it now. 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16263
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70119/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16263
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/16263
**[Test build #70119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70119/consoleFull)**
for PR 16263 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16276
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 linbojin opened a pull request:
https://github.com/apache/spark/pull/16276
[SPARK-18855][CORE] Add RDD flatten function
## What changes were proposed in this pull request?
Added a new flatten function for RDD.
## How was this patch tested?
Unit
Github user saturday-shi commented on the issue:
https://github.com/apache/spark/pull/16253
@ajbozarth @vanzin
Can anyone of you 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15915
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/15915
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70118/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15915
**[Test build #70118 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70118/consoleFull)**
for PR 15915 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16247
But yes _other_ Spark config properties would be set by the user in
sparkConfig parameter of sparkR.session method. We would just add to that like
```
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16274
**[Test build #70123 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70123/consoleFull)**
for PR 16274 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16173
Is there actually an implementation you want to do? I'd push back against
opening this up unless we have a good reason to (e.g. more scalable broadcast).
---
If your project is set up for it, you
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15915
Current change looks good to me. cc @JoshRosen @srowen to check it again.
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r92323575
--- Diff:
core/src/test/scala/org/apache/spark/storage/MemoryStoreSuite.scala ---
@@ -303,6 +303,34 @@ class MemoryStoreSuite
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r92322708
--- Diff:
core/src/test/scala/org/apache/spark/storage/MemoryStoreSuite.scala ---
@@ -303,6 +303,34 @@ class MemoryStoreSuite
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15018#discussion_r92322282
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/IsotonicRegression.scala
---
@@ -344,27 +344,30 @@ class IsotonicRegression private
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #70122 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70122/consoleFull)**
for PR 14079 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14079
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 windpiger commented on the issue:
https://github.com/apache/spark/pull/16173
cc @rxin could you help to give some advise? 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
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/16176
Thanks for the review. @cloud-fan
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16142
@AmplabJenkins retest 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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16266
**[Test build #70121 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70121/consoleFull)**
for PR 16266 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15915
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/15915
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70115/
Test PASSed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16266
Build started: [TESTS] `org.apache.spark.ShuffleSuite`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15915
**[Test build #70115 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70115/consoleFull)**
for PR 15915 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16255
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70114/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16255
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/16255
**[Test build #70114 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70114/consoleFull)**
for PR 16255 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16253
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70117/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16253
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16266
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 wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16253
**[Test build #70117 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70117/consoleFull)**
for PR 16253 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
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/14079
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70120/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #70120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70120/consoleFull)**
for PR 14079 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16264
Yup, it seems failed time to time due to network problem. FYI, there was
some discussions about this in
https://github.com/apache/spark/pull/15686#issuecomment-257217562 and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #70120 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70120/consoleFull)**
for PR 14079 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16134
#16104 merged, can you update it? 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 the issue:
https://github.com/apache/spark/pull/15717
LGTM, @gatorsmile for final sign-off
---
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/16263
**[Test build #70119 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70119/consoleFull)**
for PR 16263 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16274
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/16274
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70113/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16274
**[Test build #70113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70113/consoleFull)**
for PR 16274 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15995
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15995
thanks for the review, merging 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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/15915
```
Discovery starting.
Discovery completed in 37 seconds, 984 milliseconds.
Run starting. Expected test count is: 10
MemoryStoreSuite:
- reserve/release unroll memory
-
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15915
**[Test build #70118 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70118/consoleFull)**
for PR 15915 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16189
Jenkins retest this please
On Tue, Dec 13, 2016 at 6:13 PM UCB AMPLab wrote:
> Test FAILed.
>
>
> Refer to this link for build results (access
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16247
But yes other Spark config properties would be set by the user in
sparkConfig parameter of sparkR.session method. We would just add to that
without adding another parameter to sparkR.session
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16264
That looks like a network error when accessing github
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/16247
I mean it as something we set to the SparkContext or SparkSession and not a
parameter of sparkR.session().
---
If your project is set up for it, you can reply to this email and have your
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16264
@HyukjinKwon Could you take a look at the AppVeyor error?
---
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/16259
---
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/16275
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70116/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16275
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/16275
**[Test build #70116 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70116/consoleFull)**
for PR 16275 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16259
Merged into master and branch-2.1. 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 davies commented on the issue:
https://github.com/apache/spark/pull/16274
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 and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16273
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70112/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16273
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/16273
**[Test build #70112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70112/consoleFull)**
for PR 16273 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16275
---
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 issue:
https://github.com/apache/spark/pull/16275
Merging in master/branch-2.1.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16266
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70111/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16266
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/16266
**[Test build #70111 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70111/consoleFull)**
for PR 16266 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16253
**[Test build #70117 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70117/consoleFull)**
for PR 16253 at commit
1 - 100 of 472 matches
Mail list logo