Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15515
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/15515
**[Test build #67354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67354/consoleFull)**
for PR 15515 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15515
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67354/
Test FAILed.
---
Github user olarayej commented on the issue:
https://github.com/apache/spark/pull/11336
@felixcheung @falaki I have addressed all your comments. Shall we merge?
---
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/11336
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67351/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15515
**[Test build #67354 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67354/consoleFull)**
for PR 15515 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11336
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/11336
**[Test build #67351 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67351/consoleFull)**
for PR 11336 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15589
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/15515
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67353/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15589
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67352/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15515
**[Test build #67353 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67353/consoleFull)**
for PR 15515 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15589
**[Test build #67352 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67352/consoleFull)**
for PR 15589 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15515
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/15504
**[Test build #3368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3368/consoleFull)**
for PR 15504 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15515
**[Test build #67353 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67353/consoleFull)**
for PR 15515 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15589
**[Test build #67352 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67352/consoleFull)**
for PR 15589 at commit
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/15589
[SPARKR][branch-2.0] R merge API doc and example fix
## What changes were proposed in this pull request?
Fixes for R doc
## How was this patch tested?
N/A
You can
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/15463
Hah - I wish I had that much insight into Jenkins. I just think it was just
flaky esp. given the github DNS issues.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #67351 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67351/consoleFull)**
for PR 11336 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/15476
Thanks very much @yhuai !
---
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 markhamstra commented on the issue:
https://github.com/apache/spark/pull/15463
Whoa! Jenkins disrespects @kayousterhout -- bad Jenkins! Or did you
actually fix something @shivaram ?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14553
**[Test build #67350 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67350/consoleFull)**
for PR 14553 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15463
**[Test build #67349 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67349/consoleFull)**
for PR 15463 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11336
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67348/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #67348 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67348/consoleFull)**
for PR 11336 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11336
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 shivaram commented on the issue:
https://github.com/apache/spark/pull/15463
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15515
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67347/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #67348 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67348/consoleFull)**
for PR 11336 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15515
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/15515
**[Test build #67347 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67347/consoleFull)**
for PR 15515 at commit
Github user frreiss commented on a diff in the pull request:
https://github.com/apache/spark/pull/14553#discussion_r84539662
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -336,17 +342,27 @@ class StreamExecution(
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/15410
I would say just not displaying it would be fine, so making the `else if`
an `if`
---
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/15515
**[Test build #67347 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67347/consoleFull)**
for PR 15515 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15580
**[Test build #67344 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67344/consoleFull)**
for PR 15580 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15553
**[Test build #67345 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67345/consoleFull)**
for PR 15553 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15539
**[Test build #67346 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67346/consoleFull)**
for PR 15539 at commit
Github user frreiss commented on a diff in the pull request:
https://github.com/apache/spark/pull/14553#discussion_r84538526
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -336,17 +342,27 @@ class StreamExecution(
Github user frreiss commented on the issue:
https://github.com/apache/spark/pull/14553
I've been running tests since this morning; should have updates in soon.
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/10881
@1236897 Just try `git checkpick` this PR.
---
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 ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/15580#discussion_r84537308
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/OutputWriter.scala
---
@@ -77,19 +77,22 @@ abstract class OutputWriterFactory
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14553
@frreiss could you update the PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15476
---
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 ericl commented on the issue:
https://github.com/apache/spark/pull/15539
> The biggest problem of this proposal is, invalidating the cache may be
slow if there are a lot of cache entries.
I don't think this is really an issue. Conservatively assuming ~1us per
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15476
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/15584
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 mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/15553#discussion_r84533967
--- Diff: sql/hive-thriftserver/pom.xml ---
@@ -41,11 +41,8 @@
${project.version}
- org.apache.spark
-
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15516
I think you've committed a jar file by accident
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/15354
hi - where are we on 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 mridulm commented on the issue:
https://github.com/apache/spark/pull/15553
Changes done, please do let me know of any other comments, thanks !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15586
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/15421
merged to master and branch-2.0
---
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 tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15575
@rxin : Yes. There was a comment over there [0] but based on code it does
not look like its moving rows across input partitions (cc @chenghao-intel who
added that).
[0] :
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15421
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/15559
merged to 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
enabled and
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15576
merged to 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
enabled and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15559
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15576
---
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/15575
ExpandExec should follow child's output partitioning and ordering,
shouldn't it?
---
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 shearerp commented on the issue:
https://github.com/apache/spark/pull/15567
SPARK-14241 doesn't just occur with union and coalesce, it also occurs with
filter and probably other operations. Hopefully this PR will address all of
those situations. I strongly agree with the
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15580
cc @HyukjinKwon
---
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 JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15571
I've also merged this into `branch-2.0` (2.0.2)
---
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 nchammas commented on the issue:
https://github.com/apache/spark/pull/15567
@mengxr - I think this PR will also address
[SPARK-14241](https://issues.apache.org/jira/browse/SPARK-14241).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15571
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/15580#discussion_r84522329
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetOutputWriter.scala
---
@@ -140,16 +143,17 @@ private[parquet]
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15587
It should be the implementation to mark them as serializable, shouldn't it?
Maybe we should document it properly.
---
If your project is set up for it, you can reply to this email and have your
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15582
Actually can we move these tests into a query file test?
In sql/core/src/test/resources/sql-tests
and check SQLQueryTestSuite
---
If your project is set up for it, you can reply to
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84426029
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/NormalEquationSolver.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84437865
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/WeightedLeastSquares.scala ---
@@ -44,35 +46,52 @@ private[ml] class WeightedLeastSquaresModel(
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84433100
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/NormalEquationSolver.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84512313
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/WeightedLeastSquares.scala ---
@@ -85,73 +104,198 @@ private[ml] class WeightedLeastSquares(
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84438222
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/WeightedLeastSquares.scala ---
@@ -44,35 +46,52 @@ private[ml] class WeightedLeastSquaresModel(
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15394#discussion_r84433034
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/NormalEquationSolver.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15516
**[Test build #67342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67342/consoleFull)**
for PR 15516 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15588
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 Astralidea opened a pull request:
https://github.com/apache/spark/pull/15588
[SPARK-18039][Scheduler] fix bug maxRegisteredWaitingTime does not work
The synchronous mode of driver and executor is through dummy job is only
ensure 1 executor connect to driver.
In my
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15483
It would be good to post on the design / interfaces before you get too far.
---
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 erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15463
Thanks @kayousterhout for support but I think problem still continues. Is
there any contact to get support?
---
If your project is set up for it, you can reply to this email and have
Github user falaki commented on the issue:
https://github.com/apache/spark/pull/15421
Ping.
---
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 mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/15539#discussion_r84508947
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/TableFileCatalog.scala
---
@@ -42,24 +43,21 @@ class TableFileCatalog(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15586
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67339/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15586
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/15586
**[Test build #67339 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67339/consoleFull)**
for PR 15586 at commit
GitHub user WeichenXu123 opened a pull request:
https://github.com/apache/spark/pull/15587
[SPARK-18051][Spark Core] fix bug of custom PartitionCoalescer causing
serialization exception
## What changes were proposed in this pull request?
mark `PartitionCoalescer` and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15587
**[Test build #67341 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67341/consoleFull)**
for PR 15587 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/15463
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 have this feature
enabled and
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15463
I think Jenkins can not be triggered ;) Is there any other way to trigger?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/8849
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15436
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/15436
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67337/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15436
**[Test build #67337 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67337/consoleFull)**
for PR 15436 at commit
Github user darionyaphet closed the pull request at:
https://github.com/apache/spark/pull/15583
---
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15566#discussion_r84491905
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/rules.scala
---
@@ -209,42 +209,41 @@ case class
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15556#discussion_r84492074
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -557,7 +560,8 @@ private[history] class FsHistoryProvider(conf:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15566
**[Test build #67340 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67340/consoleFull)**
for PR 15566 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15583
+1 for not a problem if I understood this correctly.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15585
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67338/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15585
**[Test build #67338 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67338/consoleFull)**
for PR 15585 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15585
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
201 - 300 of 415 matches
Mail list logo
