Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16178
**[Test build #69821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69821/consoleFull)**
for PR 16178 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16000
> what is the benefit of force they as one API beside "it sounds correct"?
Because it pretty much ensures that when (not if) we add streaming to the
history server, it will cause breakage in
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/16139#discussion_r91422901
--- Diff: docs/ml-advanced.md ---
@@ -59,17 +59,25 @@ Given $n$ weighted observations $(w_i, a_i, b_i)$:
The number of features for each
Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
I could not agree with "The API should be one" yet
what is the benefit of force they as one API beside "it sounds correct"?
as i mention before, i can not think of any usage of
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/16122
I think that's exactly what I tried and got the `NoSuchMethodException`.
On Dec 7, 2016, at 3:35 PM, Eric Liang wrote:
I did some digging into
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16201
**[Test build #3476 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3476/consoleFull)**
for PR 16201 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16201
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16084
---
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/16204
**[Test build #69837 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69837/consoleFull)**
for PR 16204 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16084
Merging in 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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16186
LGTM pending tests
---
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 michalsenkyr commented on the issue:
https://github.com/apache/spark/pull/16201
This time I inspected both the generated Javadoc and Scaladoc. It should be
fine now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16203
**[Test build #69836 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69836/consoleFull)**
for PR 16203 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/16204
[SPARK-18775][SQL] Limit the max number of records written per file - WIP
## What changes were proposed in this pull request?
Currently, Spark writes a single file out per task, sometimes leading
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/16203
[SPARK-18774][Core][SQL]Ignore non-existing files when ignoreCorruptFiles
is enabled
## What changes were proposed in this pull request?
When `ignoreCorruptFiles` is enabled, it's better
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #69834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69834/consoleFull)**
for PR 16187 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16186
**[Test build #69835 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69835/consoleFull)**
for PR 16186 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16114
**[Test build #69833 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69833/consoleFull)**
for PR 16114 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16186#discussion_r91420339
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamingQueryListenerBus.scala
---
@@ -63,18 +83,29 @@ class
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16186#discussion_r91419929
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamingQueryListenerBus.scala
---
@@ -63,18 +83,29 @@ class
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16186#discussion_r91419859
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamingQueryListenerBus.scala
---
@@ -35,12 +43,24 @@ class
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16114#discussion_r91419246
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/KinesisRecordProcessor.scala
---
@@ -68,7 +68,16 @@ private[kinesis] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16202
**[Test build #69832 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69832/consoleFull)**
for PR 16202 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16202
@JoshRosen
---
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/16202
[SPARK-18662][hotfix] Add new resource-manager directories to SparkLauncher.
These directories are added to the classpath of applications when testing or
using SPARK_PREPEND_CLASSES, otherwise
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16202
I ran the yarn tests locally (without doing "sbt package" first) and
they're happy.
---
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/16138
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69822/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16138
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/16138
**[Test build #69822 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69822/consoleFull)**
for PR 16138 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3474 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3474/consoleFull)**
for PR 16187 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15923
**[Test build #3475 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3475/consoleFull)**
for PR 15923 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16201
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 michalsenkyr opened a pull request:
https://github.com/apache/spark/pull/16201
[SPARK-3359][DOCS] Fix grater-than symbols in Javadoc to allow building
with Java 8
## What changes were proposed in this pull request?
The API documentation build was failing when
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16186
**[Test build #69831 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69831/consoleFull)**
for PR 16186 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14638
**[Test build #69830 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69830/consoleFull)**
for PR 14638 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16200
**[Test build #69829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69829/consoleFull)**
for PR 16200 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15923
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69825/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15923
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/15923
**[Test build #69825 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69825/consoleFull)**
for PR 15923 at commit
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/16200
[SPARK-18773][core] Make commons-crypto config translation consistent.
This change moves the logic that translates Spark configuration to
commons-crypto configuration to the network-common
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14638
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16186#discussion_r91414541
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamingQueryListenerBus.scala
---
@@ -63,18 +83,29 @@ class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16199
**[Test build #69828 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69828/consoleFull)**
for PR 16199 at commit
Github user NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16199
Hello @HyukjinKwon, can you take a look at this one? I am unsure if we
should be accepting lowercased values like `nan` (versus strictly testing for
`NaN`) but I think this PR matches the
GitHub user NathanHowell opened a pull request:
https://github.com/apache/spark/pull/16199
[SPARK-18772][SQL] NaN/Infinite float parsing in JSON is inconsistent
## What changes were proposed in this pull request?
This relaxes the parsing of `Float` and `Double` columns to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69827 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69827/consoleFull)**
for PR 16165 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16179
Not sure who exactly to ping here, but let's try @cloud-fan and @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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16179
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16182
---
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/16179
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69817/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16179
**[Test build #69817 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69817/consoleFull)**
for PR 16179 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16189
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/16189
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69815/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16189
**[Test build #69815 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69815/consoleFull)**
for PR 16189 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16122
I did some digging into HiveClientImpl and Hive.java, and I think it would
be pretty safe to call `Hive.get()` within the scope of a `client.withHiveState
{ }`. That call sets the thread-local hive
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16186#discussion_r91412582
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamingQueryListenerBus.scala
---
@@ -63,18 +83,29 @@ class
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16182
Merging this to master and 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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16138
**[Test build #69826 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69826/consoleFull)**
for PR 16138 at commit
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Many thanks @squito for review.
I will address them asap ;)
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15923
**[Test build #69825 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69825/consoleFull)**
for PR 15923 at commit
Github user davies commented on the issue:
https://github.com/apache/spark/pull/15923
@JoshRosen Added a test for `detectCorrupt` is false.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16189
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69814/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16189
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/16189
**[Test build #69814 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69814/consoleFull)**
for PR 16189 at commit
Github user michalsenkyr commented on a diff in the pull request:
https://github.com/apache/spark/pull/16157#discussion_r91405625
--- Diff: docs/programming-guide.md ---
@@ -347,7 +347,7 @@ Some notes on reading files with Spark:
Apart from text files, Spark's Scala API
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69824 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69824/consoleFull)**
for PR 13579 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16182
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69811/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16182
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/16182
**[Test build #69811 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69811/consoleFull)**
for PR 16182 at commit
Github user aray commented on the issue:
https://github.com/apache/spark/pull/16161
I would be happy to create a seperate PR for adding support for
`mutable.Map` (and `List`) if that is wanted. But there is no _generic_
solution as there is no type that is assignable to both
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16150
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69820/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16150
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/16150
**[Test build #69820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69820/consoleFull)**
for PR 16150 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13579
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/13579
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69823/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69823 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69823/consoleFull)**
for PR 13579 at commit
Github user anabranch commented on a diff in the pull request:
https://github.com/apache/spark/pull/16138#discussion_r91403382
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeExpressions.scala
---
@@ -1047,6 +1047,57 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69823 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69823/consoleFull)**
for PR 13579 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16138
**[Test build #69822 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69822/consoleFull)**
for PR 16138 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3474 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3474/consoleFull)**
for PR 16187 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16178
**[Test build #69821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69821/consoleFull)**
for PR 16178 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14638
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/14638
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69816/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14638
**[Test build #69816 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69816/consoleFull)**
for PR 14638 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16198
@narendrasfo can you close the pull request as well?
---
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 michalsenkyr commented on the issue:
https://github.com/apache/spark/pull/16157
I added a few more sentences describing the cases in which the user might
want to use the argument. However, I am afraid this might be a little too
descriptive.
---
If your project is set up
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/13579
yeah, I've just got so many other distractions. Let me do it again while
tests run in different windows
---
If your project is set up for it, you can reply to this email and have your
reply
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16187
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/16150
**[Test build #69820 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69820/consoleFull)**
for PR 16150 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16119
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69819/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16119
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/16119
**[Test build #69819 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69819/consoleFull)**
for PR 16119 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16109
---
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 mallman commented on the issue:
https://github.com/apache/spark/pull/16122
I'm not sure configuration-level rollback will guarantee an absence of
interactions with other tests. For one thing, I think we need to create and
clean up an independent metastore directory for
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91394979
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/python/ExtractPythonUDFs.scala
---
@@ -166,3 +174,40 @@ object ExtractPythonUDFs extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16119
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69818/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16119
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/16119
**[Test build #69818 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69818/consoleFull)**
for PR 16119 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16187
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69812/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #69812 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69812/consoleFull)**
for PR 16187 at commit
201 - 300 of 590 matches
Mail list logo