Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15178
**[Test build #77967 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77967/testReport)**
for PR 15178 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18238
**[Test build #77966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77966/testReport)**
for PR 18238 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18262
Also, I think we need a small test to check if it really fixes 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18258
LGTM pending Jenkins
---
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 10110346 commented on the issue:
https://github.com/apache/spark/pull/18238
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/18262#discussion_r121586590
--- Diff: python/pyspark/worker.py ---
@@ -177,8 +177,13 @@ def process():
process()
except Exception:
try:
+
Github user ericsahit commented on a diff in the pull request:
https://github.com/apache/spark/pull/18268#discussion_r121586370
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -86,7 +86,12 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18268
**[Test build #77965 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77965/testReport)**
for PR 18268 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15178
**[Test build #77963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77963/testReport)**
for PR 15178 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77963/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
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/18259
**[Test build #77964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77964/testReport)**
for PR 18259 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
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/15178
**[Test build #77963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77963/testReport)**
for PR 15178 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77962/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #77962 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77962/testReport)**
for PR 17222 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14783
@catlain could you please open a JIRA.
like this, set component to SparkR
https://issues.apache.org/jira/browse/SPARK-21068?filter=12333531
---
If your project is set up for it, you can
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18075
@cloud-fan can you have a time to look at this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18284
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 ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/18284
@cloud-fan Would you mind take a look? Thanks a lot.
---
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 ConeyLiu opened a pull request:
https://github.com/apache/spark/pull/18284
[SPARK-21072] `TreeNode.mapChildren` should only apply to the children node.
## What changes were proposed in this pull request?
Just as the function name and comments of
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18283
---
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/18283
merged to master/2.2 like the other 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18283
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/18283
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77960/
Test PASSed.
---
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18271
the list is on
https://github.com/apache/spark/blob/master/R/pkg/DESCRIPTION#L20
---
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/18283
**[Test build #77960 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77960/testReport)**
for PR 18283 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/18271#discussion_r121582955
--- Diff: docs/building-spark.md ---
@@ -218,9 +218,11 @@ The run-tests script also can be limited to a specific
Python version or a speci
Github user liyichao commented on the issue:
https://github.com/apache/spark/pull/18084
OK, another scenario:
* driver with driverId1 started on worker1
* worker1 lost
* master add driverId1 to waitingDrivers
* worker1 reconnects and sends
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15240
@jiangxb1987 there's another solution to this JIRA at #15178. You can also
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17251
---
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 dataknocker closed the pull request at:
https://github.com/apache/spark/pull/18261
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17251
Thanks! Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user dataknocker commented on a diff in the pull request:
https://github.com/apache/spark/pull/18261#discussion_r121579335
--- Diff: python/pyspark/worker.py ---
@@ -178,7 +178,7 @@ def process():
except Exception:
try:
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17251
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 dataknocker commented on a diff in the pull request:
https://github.com/apache/spark/pull/18261#discussion_r121578044
--- Diff: python/pyspark/worker.py ---
@@ -178,7 +178,7 @@ def process():
except Exception:
try:
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/10506
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10506#discussion_r121576458
--- Diff:
core/src/test/scala/org/apache/spark/deploy/master/MasterSuite.scala ---
@@ -134,6 +138,71 @@ class MasterSuite extends SparkFunSuite
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/16877
Since #16620 has been merged, should we close thisï¼
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18205
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/18205
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77958/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18205
**[Test build #77958 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77958/testReport)**
for PR 18205 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #77962 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77962/testReport)**
for PR 17222 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77957/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
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 WeichenXu123 closed the pull request at:
https://github.com/apache/spark/pull/15612
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #77957 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77957/testReport)**
for PR 17222 at commit
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15240
Are you still working on this? @scwf
---
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 jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15405
Are you still working on this? @JonathanTaws
---
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/18250
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/18250
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77956/
Test PASSed.
---
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15612
Do we still want this? @WeichenXu123
---
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/18250
**[Test build #77956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77956/testReport)**
for PR 18250 at commit
Github user ll commented on the issue:
https://github.com/apache/spark/pull/18282
I am not sure if this affects pyspark but any function object serialized
with 0.2.2 or earlier cannot be deserialized with 0.3.0 or greater. I haven't
investigated making this compatible because
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18084
We should also check in Worker that we don't launch duplicate drivers, I
think the logic should be added in handling `LaunchDriver` message.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18259
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77955/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18259
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/18259
**[Test build #77955 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77955/testReport)**
for PR 18259 at commit
Github user liyichao commented on the issue:
https://github.com/apache/spark/pull/18084
Hi, add a workerId may not work. For example, this scenario:
* driver with driverId1 started on worker1
* worker1 lost
* master add driverId1 to waitingDrivers
* worker1
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121570768
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/WindowFunctionExcludeSuite.scala
---
@@ -0,0 +1,1000 @@
+/*
+ * Licensed to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18258
**[Test build #77961 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77961/testReport)**
for PR 18258 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121570373
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/expressions/WindowSpec.scala ---
@@ -113,7 +132,25 @@ class WindowSpec private[sql](
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121570239
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/expressions/WindowSpec.scala ---
@@ -113,7 +132,25 @@ class WindowSpec private[sql](
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18150
LGTM, waiting for the rebase
---
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/18283
**[Test build #77960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77960/testReport)**
for PR 18283 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18150#discussion_r121569579
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -396,6 +396,69 @@ class DAGSchedulerSuite extends SparkFunSuite
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18283
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/18283
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77959/
Test FAILed.
---
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121569249
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/windowExpressions.scala
---
@@ -262,19 +270,55 @@ object
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18283
**[Test build #77959 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77959/testReport)**
for PR 18283 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18283
**[Test build #77959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77959/testReport)**
for PR 18283 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18150#discussion_r121569075
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -396,6 +396,69 @@ class DAGSchedulerSuite extends SparkFunSuite
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/18283#discussion_r121568751
--- Diff:
core/src/test/scala/org/apache/spark/deploy/SparkSubmitSuite.scala ---
@@ -506,7 +506,7 @@ class SparkSubmitSuite
val main =
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/18283
[TEST][SPARKR][CORE] Fix broken SparkSubmitSuite
## What changes were proposed in this pull request?
Fix test file path. This is broken and undetected since R only changes
don't build
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/10506
Currently we don't cover the Driver/Executor Lost/Relaunch cases in
`MasterSuite`, and we have seen several issues related to relaunching drivers
in standalone mode, so it would be great if we
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18150#discussion_r121567987
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -188,6 +188,14 @@ class DAGScheduler(
private val
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121567532
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -1825,6 +1847,18 @@ class Analyzer(
}
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/18250#discussion_r121567491
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/csv/CSVSuite.scala
---
@@ -1174,4 +1174,33 @@ class CSVSuite extends QueryTest
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121567367
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -324,6 +324,23 @@ class Analyzer(
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12147#discussion_r121567336
--- Diff:
sql/catalyst/src/main/antlr4/org/apache/spark/sql/catalyst/parser/SqlBase.g4 ---
@@ -631,6 +631,17 @@ frameBound
| expression
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/10506
>It would be great if we can add test framework to verify the states and
statistics on the condition of Driver/Executor Lost/Join/Relaunch
@jiangxb1987 can you explain more about what you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17723
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77953/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17723
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/17723
**[Test build #77953 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77953/testReport)**
for PR 17723 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18260
Sorry I missed this part. Currently we don't externalize `ColumnVector` so
I didn't go with this direction. I'm reverting it until we have a consensus
about how to change the `ColumnVector` APIs.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18281
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/18281
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77954/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18205
**[Test build #77958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77958/testReport)**
for PR 18205 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18281
**[Test build #77954 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77954/testReport)**
for PR 18281 at commit
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18205#discussion_r121563368
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/PruneFileSourcePartitionsSuite.scala
---
@@ -66,4 +68,41 @@ class
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18250
@HyukjinKwon I tried to fix this case even in `wholeFile` mode though, I
easily couldn't do because `CSVParser` in `wholeFile` has state to parse
`InputStream` data. Once the parser hits exception,
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15306
Hm, we could it move the actual throw to the afterAll(), that would cause a
suite abort instead but presumably leave the test errors intact.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17830
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/17830
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77952/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17830
**[Test build #77952 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77952/testReport)**
for PR 17830 at commit
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18275
@srowen
This patch fails Spark unit tests. This error is not due to my code.
---
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/17222
**[Test build #77957 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77957/testReport)**
for PR 17222 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18259
**[Test build #77955 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77955/testReport)**
for PR 18259 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18250
**[Test build #77956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77956/testReport)**
for PR 18250 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/13320
Ah, ok. I'll check again.
---
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
1 - 100 of 454 matches
Mail list logo
