Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17912
**[Test build #76635 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76635/testReport)**
for PR 17912 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17879
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76621/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17879
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/17879
**[Test build #76621 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76621/testReport)**
for PR 17879 at commit
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/17911
cc @gatorsmile
---
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 hhbyyh commented on the issue:
https://github.com/apache/spark/pull/17912
cc @srowen @jkbradley @felixcheung
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17858
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76617/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17858
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/17858
**[Test build #76617 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76617/testReport)**
for PR 17858 at commit
GitHub user hhbyyh opened a pull request:
https://github.com/apache/spark/pull/17912
[SPARK-20670] [ML] Simplify FPGrowth transform
## What changes were proposed in this pull request?
As suggested by Sean Owen in https://github.com/apache/spark/pull/17130,
the transform
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16985
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/16985
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76614/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17905
**[Test build #76634 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76634/testReport)**
for PR 17905 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17905
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17910
**[Test build #76633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76633/testReport)**
for PR 17910 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16985
**[Test build #76614 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76614/testReport)**
for PR 16985 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17911
**[Test build #76632 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76632/testReport)**
for PR 17911 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/17911
[SPARK-20668][SQL] Modify ScalaUDF to handle nullability.
## What changes were proposed in this pull request?
When registering Scala UDF, we can know if the udf will return nullable
value
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
merged to master/2.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 feature
enabled and
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/17910
[SPARK-20669][ML] LogisticRegression family should be case insensitive
## What changes were proposed in this pull request?
make param `family` case insensitive
## How was this
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
ok Jenkins passes, I'm going to merge this in since there are a bunch of PR
failing because of this, even when they say it's up-to-date with master.
I'm going to investigate further though.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #76631 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76631/testReport)**
for PR 15435 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #76630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76630/testReport)**
for PR 16989 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17909
**[Test build #76629 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76629/testReport)**
for PR 17909 at commit
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/17909
[SPARK-20661][WIP] try to dump table names
## What changes were proposed in this pull request?
.. to see what tables are leaked.
Do not merge
## How was this patch
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17905
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/17905
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76612/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17905
**[Test build #76612 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76612/testReport)**
for PR 17905 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17879
**[Test build #76628 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76628/testReport)**
for PR 17879 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16985
shall we introduce a physical optimizer rule which reorders join predicates
based on `child.outputOrdering` and `outputPartitioning`?
---
If your project is set up for it, you can reply to this
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17666
LGTM.
Thank you! @maropu
---
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/17887
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/17887
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76611/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17887
**[Test build #76611 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76611/testReport)**
for PR 17887 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17865
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76625/
Test FAILed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17865
@map222 Unfortunately, our PySpark did not follow what we did in Scala.
Will review it more carefully in the future. Thanks!
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17865
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/17865
**[Test build #76625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76625/testReport)**
for PR 17865 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17908
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/15259
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76610/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15259
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/17902
**[Test build #76605 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76605/testReport)**
for PR 17902 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15259
**[Test build #76610 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76610/testReport)**
for PR 15259 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17902
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76605/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17902
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17879#discussion_r115409190
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StringIndexer.scala ---
@@ -131,6 +167,12 @@ object StringIndexer extends
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17770#discussion_r115408985
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -670,7 +671,9 @@ class Analyzer(
* Generate
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17711
**[Test build #76626 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76626/testReport)**
for PR 17711 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #76627 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76627/testReport)**
for PR 16989 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17770#discussion_r115408504
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -188,6 +188,9 @@ class Dataset[T] private[sql](
}
}
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17770#discussion_r115408432
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -47,36 +47,11 @@ abstract class LogicalPlan
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17876
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/17876
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76609/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17876
**[Test build #76609 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76609/testReport)**
for PR 17876 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
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/16989
**[Test build #76622 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76622/testReport)**
for PR 16989 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16989
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76622/
Test FAILed.
---
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17908#discussion_r115407806
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -1251,9 +1251,10 @@ class SessionCatalog(
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17908#discussion_r115407771
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/test/TestHive.scala ---
@@ -488,14 +488,9 @@ private[hive] class TestHiveSparkSession(
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17908#discussion_r115407765
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/test/TestHive.scala ---
@@ -488,14 +488,9 @@ private[hive] class TestHiveSparkSession(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17879
**[Test build #76624 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76624/testReport)**
for PR 17879 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17865
**[Test build #76625 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76625/testReport)**
for PR 17865 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17908
**[Test build #76623 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76623/testReport)**
for PR 17908 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17905
How about https://github.com/apache/spark/pull/17908? It tries to reset the
cataloged metadata objects and temporary objects.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17879
**[Test build #76621 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76621/testReport)**
for PR 17879 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #76622 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76622/testReport)**
for PR 16989 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/17908
[SPARK-20667] [SQL] [TESTS] Cleanup the cataloged metadata after completing
the package of sql/core and sql/hive
## What changes were proposed in this pull request?
So far, we do not
Github user actuaryzhang commented on the issue:
https://github.com/apache/spark/pull/17879
Thanks much @felixcheung and @viirya. I have addressed your comments.
- update from 2.2 to 2.3
- change `freq_desc` to `frequency_desc`.
- move toLowerCase to the getter method.
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17904
I'm not sure why it's failing those tests, plus my branch is up to date
with master (minus one unrelated commit)
---
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/17904
**[Test build #76620 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76620/testReport)**
for PR 17904 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17887#discussion_r115406775
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ExpressionParserSuite.scala
---
@@ -413,38 +428,102 @@ class
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17904
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/17879
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/17879
**[Test build #76619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76619/testReport)**
for PR 17879 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17879
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76619/
Test FAILed.
---
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17901#discussion_r115406526
--- Diff: R/pkg/R/functions.R ---
@@ -1752,15 +1752,15 @@ setMethod("toRadians",
#' to_date
#'
-#' Converts the column into a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17879
**[Test build #76619 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76619/testReport)**
for PR 17879 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17887#discussion_r115406428
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -1168,6 +1169,18 @@ class DatasetSuite extends QueryTest with
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
right. I think it's a good way to decouple R tests from any earlier states
and also not to mask the error/leak. I'll get that in when Jenkins pass (and
see if I could figure out what is leaked)
Github user map222 commented on the issue:
https://github.com/apache/spark/pull/17865
@gatorsmile I checked four functions, `approx_count_distinct`, `coalesce`,
`covar_samp`, and `countDistinct`, comparing the python and Scala
documentation. None of them are the same. My guess is
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
i see. I think
https://github.com/apache/spark/pull/17905/commits/d4c1a9db25ee7386f7b12e4dabb54210a9892510
is good. How about we get it checked in first (after jenkins passes)?
---
If your project
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
hmm, spoke too soon I think - looks to me like all the `withTable` clause
are in place and complete.
not sure what can be leaking through then..
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17904
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76607/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17904
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/17904
**[Test build #76607 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76607/testReport)**
for PR 17904 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
jenkins test 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 WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
@felixcheung allready updated..
---
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/17869
I think that's fine. It should be safe.
---
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17858#discussion_r115404865
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -97,12 +97,23 @@ case class InsertIntoHiveTable(
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
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 map222 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17865#discussion_r115404673
--- Diff: python/pyspark/sql/functions.py ---
@@ -153,7 +173,7 @@ def _():
# math functions that take two arguments as input
_binary_mathfunctions
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17666
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76608/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17666
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/17666
**[Test build #76608 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76608/testReport)**
for PR 17666 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17666
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
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17666
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76602/
Test PASSed.
---
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
@falaki's PR did not actually trigger that test.
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
@felixcheung you are right. That is the problem.
---
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 heary-cao commented on the issue:
https://github.com/apache/spark/pull/17869
@HyukjinKwon
I suggest to add to the beforeAllã
If the added beforeEach, Most of the unit tests will run the
Utils.clearLocalRootDirs() twice.
What do you think?
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17666
**[Test build #76602 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76602/testReport)**
for PR 17666 at commit
1 - 100 of 573 matches
Mail list logo
