Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10458#issuecomment-167009834
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10451#issuecomment-166980458
**[Test build #48248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48248/consoleFull)**
for PR 10451 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166984549
LGTM.
cc @brennonyork since I believe he also worked on this script at one point
when we were trying to replace it with some sbt functionality.
---
If your
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48377203
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,26 @@ object PushPredicateThroughJoin
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48377323
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -153,6 +153,15 @@ object SetOperationPushDown
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10456#issuecomment-166986752
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
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8531#discussion_r48378751
--- Diff: dev/test-dependencies.sh ---
@@ -0,0 +1,89 @@
+#!/usr/bin/env bash
+
+#
+# Licensed to the Apache Software Foundation (ASF) under
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10449#issuecomment-166992130
LGTM - going to merge it 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
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-167002913
Also, what about the other things expecting a `labelCol` of `DoubleType`
like the different evaluators?
Should this be handled in a follow-up jira/pr?
---
If
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10368#discussion_r48385365
--- Diff: core/src/main/scala/org/apache/spark/executor/TaskMetrics.scala
---
@@ -215,6 +215,18 @@ class TaskMetrics extends Serializable {
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48386499
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,30 @@ object PushPredicateThroughJoin
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-167007565
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
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48387575
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,30 @@ object PushPredicateThroughJoin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10458#issuecomment-167009832
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10458#issuecomment-167009752
**[Test build #48258 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48258/consoleFull)**
for PR 10458 at commit
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/10461
[SPARK-10359] Enumerate dependencies in a file and diff against it for new
pull requests
This patch adds a new build check which enumerates Spark's resolved runtime
classpath and saves it to a
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5093#issuecomment-167010151
I've taken this over at #10461, where I found a clean way to speed up the
checks to a point where they run near instantaneously without having to modify
or delete
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10448#issuecomment-166977795
**[Test build #2252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2252/consoleFull)**
for PR 10448 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166981393
This should help to avoid this problem:
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/10455
[SPARK-12508][PROJECT-INFRA] Fix minor bugs in
dev/tests/pr_public_classes.sh script
This patch fixes a handful of minor bugs in the
`dev/tests/pr_public_classes.sh` script, which is used by
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166981416
/cc @nchammas
---
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 NarineK opened a pull request:
https://github.com/apache/spark/pull/10458
[SPARK-12509] [SQL] Fixed error messages for DataFrame correlation and
covariance
I've fixed this issue by passing the function name as an argument. We could
also do the input checks separately
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10449
---
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 pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166995781
**[Test build #48253 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48253/consoleFull)**
for PR 10455 at commit
GitHub user huaxingao opened a pull request:
https://github.com/apache/spark/pull/10460
[SPARK-12459][SQL]add ExpressionDescription to string functions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huaxingao/spark spark-12459
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-167006862
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
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48387290
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,30 @@ object PushPredicateThroughJoin
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8531#discussion_r48387309
--- Diff: pom.xml ---
@@ -2052,6 +2052,22 @@
maven-deploy-plugin
2.8.2
+
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10453#issuecomment-166978436
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10453#issuecomment-166978301
**[Test build #48251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48251/consoleFull)**
for PR 10453 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10377#discussion_r48374840
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/orc/OrcSourceSuite.scala ---
@@ -174,4 +175,33 @@ class OrcSourceSuite extends OrcSuite {
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10454
[SPARK-12505] [SQL] Pushdown a Limit on top of an Outer-Join
"Rule that applies to a Limit on top of an OUTER Join. The original Limit
won't go away after applying this rule, but additional
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10454#issuecomment-166981787
**[Test build #48252 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48252/consoleFull)**
for PR 10454 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10457#issuecomment-166987525
/cc @tdas
---
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 pull request:
https://github.com/apache/spark/pull/10447#issuecomment-166987345
**[Test build #48249 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48249/consoleFull)**
for PR 10447 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10447#issuecomment-166987456
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10447#issuecomment-166987454
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10457#discussion_r48378279
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/receiver/ActorReceiver.scala
---
@@ -69,13 +68,60 @@ object ActorSupervisorStrategy {
*
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48378249
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,26 @@ object PushPredicateThroughJoin
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10457#issuecomment-166988826
**[Test build #48254 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48254/consoleFull)**
for PR 10457 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10454#issuecomment-166988730
Can you add an example in the description to illustrate this optimization?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10449#issuecomment-166992266
Although I'm fairly confident the "translation" to the new API was right,
it's ideal if Calvin or another Tachyon person can verify it first
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10454#issuecomment-166993610
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10454#issuecomment-166993615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10454#issuecomment-166993285
**[Test build #48252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48252/consoleFull)**
for PR 10454 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166995896
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10455#issuecomment-166995898
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10458#issuecomment-167000635
**[Test build #48258 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48258/consoleFull)**
for PR 10458 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10368#discussion_r48384718
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskResult.scala
---
@@ -46,6 +46,23 @@ class DirectTaskResult[T](var valueBytes: ByteBuffer,
var
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10460#issuecomment-167003289
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-167003325
**[Test build #48259 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48259/consoleFull)**
for PR 10459 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-167006026
**[Test build #48264 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48264/consoleFull)**
for PR 10459 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167047677
**[Test build #48288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48288/consoleFull)**
for PR 10368 at commit
GitHub user yuzhanghan1982 opened a pull request:
https://github.com/apache/spark/pull/10467
Branch 1.6
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dukedbgroup/spark branch-1.6
Alternatively you can review and apply these
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167050810
**[Test build #48285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48285/consoleFull)**
for PR 10463 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167056106
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167056107
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/8915#issuecomment-167058985
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
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/10272#issuecomment-167059047
Current implementation still outperforms the one from
https://github.com/utcompling/Scalabha/blob/master/src/main/scala/opennlp/scalabha/lang/eng/PorterStemmer.scala,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8915#issuecomment-167059552
**[Test build #48295 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48295/consoleFull)**
for PR 8915 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167044200
@maropu I agree that can be another way! but I just think an interface
should be inclusive not exclusive. Handing in `ParquetRelation` might mean
other datasources
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167046527
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
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167046506
```
[info] PostgresIntegrationSuite:
[info] Exception encountered when attempting to run a suite with class
name:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9992#issuecomment-167048778
**[Test build #48289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48289/consoleFull)**
for PR 9992 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167050979
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167051327
**[Test build #48290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48290/consoleFull)**
for PR 10427 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167050976
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9992#issuecomment-167055004
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9992#issuecomment-167055003
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9992#issuecomment-167054764
**[Test build #48289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48289/consoleFull)**
for PR 9992 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167056049
**[Test build #48286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48286/consoleFull)**
for PR 10463 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167061036
**[Test build #48288 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48288/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167061069
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167063931
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167063911
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167063904
**[Test build #48291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48291/consoleFull)**
for PR 10435 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167063910
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167063932
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167043478
**[Test build #48286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48286/consoleFull)**
for PR 10463 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10466#issuecomment-167044370
**[Test build #48284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48284/consoleFull)**
for PR 10466 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10466#issuecomment-167044425
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10466#issuecomment-167044424
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10465#issuecomment-167045672
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10465#issuecomment-167045673
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10465#issuecomment-167045613
**[Test build #48282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48282/consoleFull)**
for PR 10465 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167046672
**[Test build #48287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48287/consoleFull)**
for PR 10427 at commit
Github user mwws commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-167052293
@squito @mridulm I am afraid an additional state can not help here, your
use case requires "TaskSet related nodeBlacklist" which is not supported with
current
GitHub user maropu opened a pull request:
https://github.com/apache/spark/pull/10468
[SPARK-12409][SPARK-12387][SPARK-12391][SQL] Support AND/OR/IN/LIKE
push-down filters for JDBC
This is rework from #10386 and add more tests and LIKE push-down support.
You can merge this pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167060472
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167060473
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-167060381
**[Test build #48287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48287/consoleFull)**
for PR 10427 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10454#discussion_r48400022
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -858,6 +859,30 @@ object PushPredicateThroughJoin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167044665
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167055194
**[Test build #48291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48291/consoleFull)**
for PR 10435 at commit
Github user zhichao-li commented on a diff in the pull request:
https://github.com/apache/spark/pull/9589#discussion_r48398910
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/ClientWrapper.scala ---
@@ -151,29 +152,34 @@ private[hive] class ClientWrapper(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9350#issuecomment-167058892
**[Test build #48292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48292/consoleFull)**
for PR 9350 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10330#issuecomment-167059780
**[Test build #48296 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48296/consoleFull)**
for PR 10330 at commit
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/4399#issuecomment-167042951
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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10463#issuecomment-167043114
add to whitelist.
---
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 pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167044643
**[Test build #48283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48283/consoleFull)**
for PR 10368 at commit
301 - 400 of 437 matches
Mail list logo
