Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16307
**[Test build #70241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70241/testReport)**
for PR 16307 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16307#discussion_r92765013
--- Diff:
common/unsafe/src/main/java/org/apache/spark/unsafe/types/CalendarInterval.java
---
@@ -252,7 +252,7 @@ public static long
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/16307
[MINOR][BUILD] Fix lint-check failures and javadoc8 break
## What changes were proposed in this pull request?
This PR proposes to fix lint-check failures and javadoc8 break.
Github user ankurdave commented on the issue:
https://github.com/apache/spark/pull/16271
Merged into 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16304
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/16304
**[Test build #70233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70233/testReport)**
for PR 16304 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16304
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70233/
Test FAILed.
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16271
---
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 qhhan closed the pull request at:
https://github.com/apache/spark/pull/16306
---
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 qhhan opened a pull request:
https://github.com/apache/spark/pull/16306
Branch 2.1
## 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 patch
Github user ankurdave commented on the issue:
https://github.com/apache/spark/pull/16271
Thanks @aray for the explanation. I agree with @srowen - this looks
reasonable to me. I'm going to merge it.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16305
cc @srowen, Could you please take a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16282
**[Test build #70240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70240/testReport)**
for PR 16282 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16305#discussion_r92762998
--- Diff: core/src/main/scala/org/apache/spark/deploy/RPackageUtils.scala
---
@@ -231,8 +236,10 @@ private[deploy] object RPackageUtils extends Logging
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16305
Build started: [TESTS]
`org.apache.spark.scheduler.EventLoggingListenerSuite`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16305
**[Test build #70238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70238/testReport)**
for PR 16305 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16261
**[Test build #70239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70239/testReport)**
for PR 16261 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16261
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16305#discussion_r92761800
--- Diff: core/src/main/scala/org/apache/spark/deploy/RPackageUtils.scala
---
@@ -231,8 +236,10 @@ private[deploy] object RPackageUtils extends Logging
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16261#discussion_r92761816
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Task.scala ---
@@ -58,13 +60,17 @@ private[spark] abstract class Task[T](
val stageId:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16305#discussion_r92761717
--- Diff: core/src/main/scala/org/apache/spark/deploy/RPackageUtils.scala
---
@@ -176,26 +176,31 @@ private[deploy] object RPackageUtils extends Logging
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/16305
[SPARK-18895][TESTS] Fix resource-closing-related and path-related test
failures in identified ones on Windows
## What changes were proposed in this pull request?
There are several
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16261
With the help of @kayousterhout I ran a scheduling microbenchmark (Code
[1]) with 1 tasks per stage on 20 m2.4xlarge machines on EC2 (160 cores).
From 10 trials, I measured the average time
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16290#discussion_r92761572
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -964,11 +970,17 @@ object StaticSQLConf {
}
}
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/16233
cc @yhuai @cloud-fan Please have a look at this when you have time. 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
Github user xuanyuanking commented on the issue:
https://github.com/apache/spark/pull/16135
cc @rxin thanks for check.
---
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 hhbyyh commented on the issue:
https://github.com/apache/spark/pull/15211
Remove WIP.
---
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 wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16294#discussion_r92757455
--- Diff: docs/structured-streaming-programming-guide.md ---
@@ -671,12 +678,114 @@ windowedCounts = words.groupBy(
+### Handling
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14868
Although the function returns the approximate percentile, the result is
still deterministic. Is my understanding right?
---
If your project is set up for it, you can reply to this email and
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16304#discussion_r92756861
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -572,6 +572,10 @@ class Dataset[T] private[sql](
val parsedDelay =
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16300
---
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/16300
Merging in master/branch-2.1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16300
**[Test build #70237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70237/testReport)**
for PR 16300 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16300
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16300
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
enabled and wishes so, or if the
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16300
hm weird that we hard coded the name.
---
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/16290
**[Test build #70236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70236/testReport)**
for PR 16290 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16300
Could we also update [another two more
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16249
**[Test build #70235 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70235/testReport)**
for PR 16249 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16249
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/16249
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70235/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16282
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/16282
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70229/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16282
**[Test build #70229 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70229/testReport)**
for PR 16282 at commit
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/16291
@vanzin - Thanks for taking a look and sorry about putting my unfinished
sloppy code out there. I updated the bug and the PR with the overall design
idea, which hopefully will answer your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16301
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/16301
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70234/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16301
**[Test build #70234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70234/testReport)**
for PR 16301 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16300
**[Test build #3502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3502/testReport)**
for PR 16300 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16304#discussion_r92754420
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -572,6 +572,10 @@ class Dataset[T] private[sql](
val parsedDelay =
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16249
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16249
**[Test build #70226 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70226/consoleFull)**
for PR 16249 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16249
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70226/
Test FAILed.
---
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/16304#discussion_r92753969
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -572,6 +572,10 @@ class Dataset[T] private[sql](
val parsedDelay =
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/16304#discussion_r92753590
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -572,6 +572,10 @@ class Dataset[T] private[sql](
val parsedDelay =
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16249
**[Test build #70235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70235/testReport)**
for PR 16249 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16304
event time?
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16301
**[Test build #70234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70234/testReport)**
for PR 16301 at commit
Github user ryan-williams commented on the issue:
https://github.com/apache/spark/pull/16303
I appreciate the quick turn-around on this, though it seems like a mis-use
of the `provided` scope.
FWIW, I am advocating for:
- `mv
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16142
> I just add a new clean-up mode, but not add the cleaner itself.
But that's kinda the point. How many different ways of cleaning need to be
added? Will this one be enough? Will people ask
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/16281
The improvement is in how row groups are garbage collected. G1GC puts
humongous allocations directly into the old generation, so you end up needing a
full GC to reclaim the space. That just
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15211
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/15211
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70232/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15211
**[Test build #70232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70232/testReport)**
for PR 15211 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16303
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70228/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16303
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/16303
**[Test build #70228 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70228/testReport)**
for PR 16303 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16173
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/16173
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70227/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16282
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/16282
**[Test build #70219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70219/testReport)**
for PR 16282 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16282
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70219/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16173
**[Test build #70227 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70227/testReport)**
for PR 16173 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16232
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70230/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16232
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/16232
**[Test build #70230 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70230/testReport)**
for PR 16232 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/16281
@rdblue Interesting, do you have any estimated or actual data for
performance improvement?
I am interested in how you can achieve performance improvement over
`byte[]`.
- Usage of
Github user cenyuhai commented on the issue:
https://github.com/apache/spark/pull/15109
Ok, I will close this PR. This is not a big 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
Github user cenyuhai closed the pull request at:
https://github.com/apache/spark/pull/15109
---
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/16304
**[Test build #70233 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70233/testReport)**
for PR 16304 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16304#discussion_r92746039
--- Diff:
common/unsafe/src/main/java/org/apache/spark/unsafe/types/CalendarInterval.java
---
@@ -252,6 +252,9 @@ public static long parseSecondNano(String
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/16304
[SPARK-18894][SS] Follow-up bug fix
## What changes were proposed in this pull request?
Two changes
- Disallow went time watermark delay threshold be specified in months or
years
-
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15211
**[Test build #70232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70232/testReport)**
for PR 15211 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16300
**[Test build #3502 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3502/testReport)**
for PR 16300 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16285
Thanks for looking into it. In that case, maybe we should just keep the
thing as is and don't change it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16253
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70231/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16253
**[Test build #70231 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70231/testReport)**
for PR 16253 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16253
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16300
cc @cloud-fan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16299
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/16299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70222/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16299
**[Test build #70222 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70222/testReport)**
for PR 16299 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16300
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/16300
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70223/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16300
**[Test build #70223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70223/testReport)**
for PR 16300 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70220/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16299
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/16299
**[Test build #70220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70220/testReport)**
for PR 16299 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16253
**[Test build #70231 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70231/testReport)**
for PR 16253 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70221/
Test PASSed.
---
1 - 100 of 470 matches
Mail list logo
