GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10393
[SPARK-12441] [SQL] Fixing missingInput in Generate
When explain any plan with Generate, we will see an exclamation mark in the
plan. Normally, when we see this mark, it means the plan has an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166017392
**[Test build #48056 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48056/consoleFull)**
for PR 10393 at commit
Github user keithchambers commented on the pull request:
https://github.com/apache/spark/pull/10366#issuecomment-166001787
@andrewor14 makes sense. Thank you!
---
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/9553#issuecomment-166017558
**[Test build #48057 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48057/consoleFull)**
for PR 9553 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r48095511
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -132,6 +132,7 @@ class SparkILoop(
@DeveloperApi
var
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r48095491
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1026,17 +1027,30 @@ class SparkILoop(
@DeveloperApi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166016740
**[Test build #48055 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48055/consoleFull)**
for PR 10393 at commit
Github user xguo27 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r48095871
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1026,17 +1027,30 @@ class SparkILoop(
@DeveloperApi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9553#issuecomment-166025910
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/9553#issuecomment-166025617
**[Test build #48057 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48057/consoleFull)**
for PR 9553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9553#issuecomment-166025914
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/10368#issuecomment-166032102
**[Test build #48059 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48059/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-165997773
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/10368#issuecomment-165997757
**[Test build #48053 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48053/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-165997771
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166022745
**[Test build #48056 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48056/consoleFull)**
for PR 10393 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166022788
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/10393#issuecomment-166022790
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r48095548
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1026,17 +1027,30 @@ class SparkILoop(
@DeveloperApi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166028352
**[Test build #48058 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48058/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166004451
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/10156#issuecomment-166010389
**[Test build #48054 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48054/consoleFull)**
for PR 10156 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10156#issuecomment-166017714
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 BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10327#discussion_r48093699
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/PCA.scala ---
@@ -167,14 +167,37 @@ object PCAModel extends MLReadable[PCAModel] {
Github user yanakad commented on the pull request:
https://github.com/apache/spark/pull/10379#issuecomment-166020526
@liancheng Would logging the fail paths at WARN or ERROR level be an
acceptable compromise? I am not sure if you're advising that the fix is not
good enough or if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166022587
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/10393#issuecomment-166022588
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/10368#issuecomment-166028405
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166028404
**[Test build #48058 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48058/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166028406
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user pierre-borckmans opened a pull request:
https://github.com/apache/spark/pull/10392
[SPARK-12440] - [core] - Avoid setCheckpoint warning when directory is not
local
In SparkContext method `setCheckpointDir`, a warning is issued when spark
master is not local and the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10394#issuecomment-166033288
**[Test build #48062 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48062/consoleFull)**
for PR 10394 at commit
Github user huaxingao commented on the pull request:
https://github.com/apache/spark/pull/10262#issuecomment-166033287
@yhuai
JDBCSuite uses H2 database. It seems that for char(n) data type, either H2
database doesn't pad, or the H2 JDBC driver already trims the empty space for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166033913
**[Test build #2237 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2237/consoleFull)**
for PR 10395 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10396
[SPARK-12292] [SQL] Support UnsafeRow in Generator.
After the fix, unsafe->safe convertors are not inserted between Generate
and its Child.
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166046558
**[Test build #2238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2238/consoleFull)**
for PR 10396 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166046577
**[Test build #2240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2240/consoleFull)**
for PR 10395 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166046550
**[Test build #2238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2238/consoleFull)**
for PR 10396 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166046523
**[Test build #2239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2239/consoleFull)**
for PR 10368 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166046574
**[Test build #2240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2240/consoleFull)**
for PR 10395 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166046525
**[Test build #2239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2239/consoleFull)**
for PR 10368 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166061058
**[Test build #48068 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48068/consoleFull)**
for PR 10368 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166068833
cc @pwendell
---
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 BenFradet commented on the pull request:
https://github.com/apache/spark/pull/10327#issuecomment-165997370
lgtm except one minor doc comment.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10156#issuecomment-166017716
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/10156#issuecomment-166017682
**[Test build #48054 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48054/consoleFull)**
for PR 10156 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-166022565
**[Test build #48055 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48055/consoleFull)**
for PR 10393 at commit
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10284#issuecomment-166033110
I think the following exception seen in unit test run was related to this
PR:
```
[info] - Simple replay (70 milliseconds)
java.lang.NullPointerException
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166059915
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166059903
**[Test build #48067 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48067/consoleFull)**
for PR 10368 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166069977
retest it 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10398#issuecomment-166070873
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/10398#issuecomment-166070849
**[Test build #48069 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48069/consoleFull)**
for PR 10398 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10398#issuecomment-166070874
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/10399
[SPARK-12443][SQL] encoderFor should support Decimal
JIRA: https://issues.apache.org/jira/browse/SPARK-12443
`constructorFor` will call `dataTypeFor` to determine if a type is
`ObjectType`
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10387
---
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 pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166033075
cc @ankurdave
---
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 opened a pull request:
https://github.com/apache/spark/pull/10395
[SPARK-11808] Remove Bagel.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark SPARK-11808
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10394#issuecomment-166033995
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10394#issuecomment-166033988
**[Test build #48062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48062/consoleFull)**
for PR 10394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10394#issuecomment-166033996
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10397
HOTFIX: Build testing failed.
```
./dev/run-tests.py
File "./dev/run-tests.py", line 532
if not changed_files or any(f.endswith(".py") for f in changed_files):
^
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166047424
retest it 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 holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/10150#discussion_r48097828
--- Diff: python/pyspark/mllib/clustering.py ---
@@ -38,13 +38,158 @@
from pyspark.mllib.util import Saveable, Loader, inherit_doc, JavaLoader,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166033822
**[Test build #2237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2237/consoleFull)**
for PR 10395 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10387#issuecomment-166033666
cc @JoshRosen I had to disable java style checker using a hotfix commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166033780
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166040219
retest it 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 rxin opened a pull request:
https://github.com/apache/spark/pull/10394
[SPARK-2331] SparkContext.emptyRDD should return RDD[T] not EmptyRDD[T]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark SPARK-2331
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166034111
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/10368#issuecomment-166034112
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/10368#issuecomment-166034107
**[Test build #48063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48063/consoleFull)**
for PR 10368 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166034110
**[Test build #48063 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48063/consoleFull)**
for PR 10368 at commit
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/9263#issuecomment-166042934
@zsxwing Are there some changes you would like to see to this pull request?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166050276
**[Test build #48066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48066/consoleFull)**
for PR 10395 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166055247
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166059382
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/10395#issuecomment-166059383
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/10368#issuecomment-166059917
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10398
[SPARK-12287] [SQL] Support Unsafe Row in MapPartitions/MapGroups/CoGroup
Support Unsafe Row in MapPartitions/MapGroups/CoGroup.
Added a test case for MapPartitions. Since MapGroups
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166069156
LGTM (I downloaded your PR and did some grepping to make sure there are no
references). One other thing that occured to me is someone could easily create
a package
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166070595
Test FAILed.
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/10395#issuecomment-166033472
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/10395#issuecomment-166033473
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/10395#issuecomment-166033471
**[Test build #48061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48061/consoleFull)**
for PR 10395 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166041205
@rxin Could you also comment it out the first line? Thanks!
```python
if not changed_files or any(f.endswith(".java") for f in changed_files):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10397#issuecomment-166046107
**[Test build #48065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48065/consoleFull)**
for PR 10397 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10397#issuecomment-166046053
I pushed directly to master and fixed it. 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 your
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/9710#issuecomment-166046164
@JoshRosen Please review.
---
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 gatorsmile closed the pull request at:
https://github.com/apache/spark/pull/10397
---
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 pull request:
https://github.com/apache/spark/pull/10397#issuecomment-166046802
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 your project does not have this feature
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166052576
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10396#issuecomment-166052820
retest it 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166055164
**[Test build #48067 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48067/consoleFull)**
for PR 10368 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10397#issuecomment-166058780
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/10397#issuecomment-166058781
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/10397#issuecomment-166058753
**[Test build #48065 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48065/consoleFull)**
for PR 10397 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10262#issuecomment-166058803
I guess we can try to add a docker test. Can you try to add one in
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-166060830
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-166060825
HeartbeatReceiverSuite.'expire dead hosts' failed
Doesn't seem to be related to the PR.
---
If your project is set up for it, you can reply to this email and
1 - 100 of 152 matches
Mail list logo
