Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13603
**[Test build #61116 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61116/consoleFull)**
for PR 13603 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/13603
actually, calling it a flaky test is unfair -- really spark itself was
flaky, the behavior was not reliable when you had locality + blacklists, you
might think the taskSet was unschedulable, though
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13745
**[Test build #61115 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61115/consoleFull)**
for PR 13745 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/13745#discussion_r68248732
--- Diff: examples/src/main/python/ml/quantile_discretizer_example.py ---
@@ -29,11 +29,12 @@
# $example on$
data = [(0, 18.0,), (1, 19.0,),
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/13712
other then the minor doc changes it looks good. It might be nice to test
compile against older version of hadoop just as test.
---
If your project is set up for it, you can reply to this email
Github user GayathriMurali commented on a diff in the pull request:
https://github.com/apache/spark/pull/13745#discussion_r68245367
--- Diff: examples/src/main/python/ml/quantile_discretizer_example.py ---
@@ -29,11 +29,12 @@
# $example on$
data = [(0, 18.0,), (1,
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13680
@cloud-fan , I have one question about null field. Should we put zero into
the corresponding field to position where ```setNullAt()``` is called as
```UnsafeRow```
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/13874#discussion_r68242692
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/parser/ParserUtils.scala
---
@@ -39,8 +39,8 @@ object ParserUtils {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13839
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61114/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13839
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/13839
**[Test build #61114 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61114/consoleFull)**
for PR 13839 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/13712
I just enabled rolling log aggregation in yarn side and run the application
with this patch on to see if log is actually aggregated periodically.
---
If your project is set up for it, you can
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/13712#discussion_r68241098
--- Diff: docs/running-on-yarn.md ---
@@ -472,6 +472,28 @@ To use a custom metrics.properties for the application
master and executors, upd
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13846#discussion_r68240312
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -206,15 +205,33 @@ object RemoveAliasOnlyProject
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13850
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/13712
@jerryshao what exactly did you do for testing 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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/13850
+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 wishes so, or if the
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/11560
I hadn't planned on it because it is not a bug fix, so normally doesn't go
in a maintenance release
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/13338
I really want to get this into the 2.0 release since its a change in
behavior if you don't have time I'll put up pr with minor changes.
---
If your project is set up for it, you can reply
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/13338
ping @rdblue
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/13482
ping @rdblue do you have time to update 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13839
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/13839
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61113/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13839
**[Test build #61113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61113/consoleFull)**
for PR 13839 at commit
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/11560
Sean, any plans to backport this and
https://issues.apache.org/jira/browse/SPARK-5814 to the 1.6 branch? Happy to
test and contribute myself in a new JIRA if need be
---
If your project is set
Github user NarineK commented on a diff in the pull request:
https://github.com/apache/spark/pull/13760#discussion_r68227494
--- Diff: R/pkg/R/group.R ---
@@ -199,17 +199,10 @@ createMethods()
#' Applies a R function to each group in the input GroupedData
#'
#'
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13846#discussion_r68225020
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -206,15 +205,33 @@ object RemoveAliasOnlyProject
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13839
**[Test build #61114 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61114/consoleFull)**
for PR 13839 at commit
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/13871
LGTM except for the compilation 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 have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13841
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/13841
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61112/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13841
**[Test build #61112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61112/consoleFull)**
for PR 13841 at commit
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/13872
My major concern is that even the reported case is "fixed" by this PR, in
general user applications shouldn't rely on predicate evaluation order. Other
than that, the change made in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13839
**[Test build #61113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61113/consoleFull)**
for PR 13839 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13873
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/13873
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/6/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13873
**[Test build #6 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/6/consoleFull)**
for PR 13873 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13841
**[Test build #61112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61112/consoleFull)**
for PR 13841 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13834
I think the failure is legit. It's stuck at:
```
[info] ScriptTransformationSuite:
Attempting to post to Github...
Exception in thread "Thread-ScriptTransformation-Feed"
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13834
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/13834
**[Test build #61103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61103/consoleFull)**
for PR 13834 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13834
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61103/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13865
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/13865
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61109/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13865
**[Test build #61109 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61109/consoleFull)**
for PR 13865 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13873
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61108/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13873
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/13873
**[Test build #61108 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61108/consoleFull)**
for PR 13873 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68210614
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -327,6 +329,50 @@ class StreamingContextSuite extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68210568
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -327,6 +329,50 @@ class StreamingContextSuite extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68210436
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -327,6 +329,50 @@ class StreamingContextSuite extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68210255
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -327,6 +329,50 @@ class StreamingContextSuite extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68210240
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -327,6 +329,50 @@ class StreamingContextSuite extends
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13866#discussion_r68209882
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -18,10 +18,12 @@
package
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13875
@huangbiyu please close 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 and
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/11765
Same, is this still an issue, active?
---
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/13875
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 srowen commented on the issue:
https://github.com/apache/spark/pull/7278
I think we might not end up merging this given the discussion here and on
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 srowen commented on the issue:
https://github.com/apache/spark/pull/11854
@gatorsmile can this be closed for now?
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13730
Hi, @tdas .
Could you give me some advice for the direction about how to change this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/11598
Thank you, though given the lack of activity, I don't think this would be
merged into Spark. It's here for the record and you can close this PR.
---
If your project is set up for it, you can reply
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/8625
Given lack of follow up, and activity in GraphX, I think this is probably
wont-fix for Spark, though it could go into an external library (and lives here
for anyone interested). I think it can be
GitHub user huangbiyu opened a pull request:
https://github.com/apache/spark/pull/13875
update
## 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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13403
Thank you for everything, @srowen , @mengxr , @rxin .
---
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/13403
---
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/13403
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13873
**[Test build #6 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/6/consoleFull)**
for PR 13873 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13870
Hi, @liancheng .
Could you review this PR, too?
This was initially introduced in your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13403
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61106/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13403
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/13403
**[Test build #61106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61106/consoleFull)**
for PR 13403 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13624
I think this is correct and can see why it's faster.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13624#discussion_r68205142
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/GradientBoostedTrees.scala
---
@@ -205,31 +205,31 @@ private[spark] object GradientBoostedTrees
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r68204608
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/FileSourceStrategy.scala
---
@@ -109,108 +111,45 @@ private[sql] object
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13874
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/13874
**[Test build #61110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61110/consoleFull)**
for PR 13874 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13874
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61110/
Test FAILed.
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13624#discussion_r68203172
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/GradientBoostedTrees.scala
---
@@ -205,31 +205,31 @@ private[spark] object GradientBoostedTrees
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13624#discussion_r68202993
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/GradientBoostedTrees.scala
---
@@ -205,31 +205,31 @@ private[spark] object GradientBoostedTrees
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13624#discussion_r68202942
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/GradientBoostedTrees.scala
---
@@ -205,31 +205,31 @@ private[spark] object GradientBoostedTrees
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13874
**[Test build #61110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61110/consoleFull)**
for PR 13874 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13874
cc @hvanhovell
---
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/13874
[SQL][minor] ParserUtils.operationNotAllowed should throw exception directly
## What changes were proposed in this pull request?
It's weird that `ParserUtils.operationNotAllowed` returns
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13865
**[Test build #61109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61109/consoleFull)**
for PR 13865 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13872
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61105/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13872
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/13872
**[Test build #61105 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61105/consoleFull)**
for PR 13872 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13756
I'm thinking about if it's possible to concentrate error checking logics at
one place for table creation. For example, we check duplicated table column
names at parser for SQL
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13872
For any conclusion, thank you for review, @mengxr and @liancheng !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13839
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/13839
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61102/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13839
**[Test build #61102 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61102/consoleFull)**
for PR 13839 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13873
**[Test build #61108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61108/consoleFull)**
for PR 13873 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13836
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61101/
Test PASSed.
---
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/13873
[SPARK-16167][SQL] RowEncoder should preserve array/map type nullability.
## What changes were proposed in this pull request?
Currently `RowEncoder` doesn't preserve nullability of
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13859
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61107/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13836
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/13859
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/13859
**[Test build #61107 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61107/consoleFull)**
for PR 13859 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13836
**[Test build #61101 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61101/consoleFull)**
for PR 13836 at commit
301 - 400 of 475 matches
Mail list logo
