Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111989382
Merged build started.
---
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/6779#issuecomment-111989380
Merged build started.
---
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/6394#issuecomment-111989384
Merged build started.
---
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/6824#issuecomment-111989385
Merged build started.
---
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/6822#issuecomment-111989345
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/6822#issuecomment-111989316
[Test build #34920 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34920/console)
for PR 6822 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-111997343
Merged build triggered.
---
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/6825#issuecomment-111997405
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6763#issuecomment-112001537
[Test build #34934 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34934/consoleFull)
for PR 6763 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112020029
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112020724
Merged build triggered.
---
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6825#discussion_r32410987
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -356,15 +367,11 @@ case class MaxOf(left:
Github user carsonwang commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-111989257
Thanks @jerryshao . I updated the code as suggested.
---
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 pull request:
https://github.com/apache/spark/pull/6826#issuecomment-111998304
[Test build #34927 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34927/console)
for PR 6826 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6763#issuecomment-112000891
Merged build started.
---
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/6763#issuecomment-112000863
Merged build triggered.
---
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/6827#issuecomment-112022587
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/6827#issuecomment-112022559
[Test build #34928 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34928/console)
for PR 6827 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6828#issuecomment-111984097
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111986910
@jerryshao I think due to the data loss bug, we can call zero is a illegal
setting.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-111989597
Merged build started.
---
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/6826#issuecomment-111989383
Merged build started.
---
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/6823#issuecomment-111989381
Merged build started.
---
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/6394#issuecomment-111989378
Merged build started.
---
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/6827#issuecomment-111989379
Merged build started.
---
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/6827#issuecomment-111989525
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111989485
[Test build #34929 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34929/consoleFull)
for PR 6818 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-111989386
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6460#issuecomment-111995615
[Test build #34932 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34932/consoleFull)
for PR 6460 at commit
Github user hotienvu commented on the pull request:
https://github.com/apache/spark/pull/5533#issuecomment-112006961
Hi, I'm running Spark job UI under virtual hosts since I can't open any
port rather than 80 for security reason. Using spark.ui.proxyBase has been
working at least
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-112016874
[Test build #34933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34933/console)
for PR 6825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-112016896
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 jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32400880
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -282,8 +282,14 @@ private[history] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-111998049
[Test build #34933 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34933/consoleFull)
for PR 6825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-111998349
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 catap commented on the pull request:
https://github.com/apache/spark/pull/4456#issuecomment-112031406
@jkbradley, @srowen do you have any news?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-111989545
[Test build #34928 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34928/consoleFull)
for PR 6827 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-111990123
[Test build #34930 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34930/consoleFull)
for PR 6827 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-111990868
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/6779#issuecomment-111990930
[Test build #34922 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34922/console)
for PR 6779 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6779#issuecomment-111990939
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/6825#issuecomment-111990866
[Test build #34923 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34923/console)
for PR 6825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112020785
Merged build started.
---
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/6394#issuecomment-112021133
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/6827#issuecomment-112023442
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/6827#issuecomment-112023364
[Test build #34930 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34930/console)
for PR 6827 at commit
GitHub user yijieshen opened a pull request:
https://github.com/apache/spark/pull/6828
[SPARK-8283][SQL] Resolve udf_struct test failure in HiveCompatibilitySuite
This PR aimed to resolve udf_struct test failure in HiveCompatibilitySuite.
Currently, this is done by loosening
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6460#issuecomment-112017288
[Test build #34932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34932/console)
for PR 6460 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6460#issuecomment-112017314
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/6763#issuecomment-112030078
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/6763#issuecomment-112030001
[Test build #34934 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34934/console)
for PR 6763 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6460#issuecomment-111994066
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6721#issuecomment-111984474
[Test build #34914 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34914/console)
for PR 6721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6721#issuecomment-111984558
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/6823#issuecomment-111990269
[Test build #34921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34921/consoleFull)
for PR 6823 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-111990308
[Test build #34923 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34923/consoleFull)
for PR 6825 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111990264
[Test build #34929 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34929/console)
for PR 6818 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-111990231
[Test build #34926 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34926/consoleFull)
for PR 6394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111990274
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/6394#issuecomment-111990238
[Test build #34925 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34925/consoleFull)
for PR 6394 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6779#issuecomment-111990267
[Test build #34922 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34922/consoleFull)
for PR 6779 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-112022212
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/6394#issuecomment-112022161
[Test build #34925 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34925/console)
for PR 6394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6824#issuecomment-112023917
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/6818#issuecomment-112023823
[Test build #34931 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34931/console)
for PR 6818 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111985469
Why not change the title? I think the problem here is illegal setting of
configuration, not actually data loss bug.
---
If your project is set up for it, you can
Github user XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/6817#issuecomment-111985278
@sryza @andrewor14 Can you have 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6824#issuecomment-111990552
[Test build #34924 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34924/consoleFull)
for PR 6824 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-111990689
[Test build #34927 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34927/consoleFull)
for PR 6826 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111994741
[Test build #34931 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34931/consoleFull)
for PR 6818 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-112020960
[Test build #34926 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34926/console)
for PR 6394 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112021353
[Test build #34935 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34935/consoleFull)
for PR 6826 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6824#issuecomment-112023895
[Test build #34924 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34924/console)
for PR 6824 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-112023851
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6825#discussion_r32410564
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -341,9 +341,20 @@ case class MaxOf(left:
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32400966
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -282,8 +282,14 @@ private[history] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6818#issuecomment-111994067
Merged build started.
---
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/6818#issuecomment-111993951
Merged build triggered.
---
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/6460#issuecomment-111993962
Merged build triggered.
---
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/6823#issuecomment-112021951
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/6823#issuecomment-112021904
[Test build #34921 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34921/console)
for PR 6823 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112039618
Merged build triggered.
---
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 zsxwing opened a pull request:
https://github.com/apache/spark/pull/6829
[SPARK-8376][Docs]Add common lang3 to the Spark Flume Sink doc
Commons Lang 3 has been added as one of the dependencies of Spark Flume
Sink since #5703. This PR updates the doc for it.
You can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112039637
Merged build started.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6761#discussion_r32417054
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -113,6 +106,55 @@ class NaiveBayesModel private[mllib] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112064813
Merged build triggered.
---
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/6826#issuecomment-112064837
Merged build started.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6761#discussion_r32418240
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -113,6 +106,55 @@ class NaiveBayesModel private[mllib] (
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112068466
OK but surely it's easier to make an assembly target than tell people they
have to piece together the dependencies and keep updating docs about it?
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112073204
[Test build #34940 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34940/consoleFull)
for PR 6762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112061324
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6761#discussion_r32417097
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -113,6 +106,55 @@ class NaiveBayesModel private[mllib] (
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112069201
[Test build #34938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34938/consoleFull)
for PR 6762 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6823#issuecomment-112073237
[Test build #34939 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34939/consoleFull)
for PR 6823 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112069615
[Test build #34938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34938/console)
for PR 6762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112069620
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/6826#issuecomment-112061170
[Test build #34935 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34935/console)
for PR 6826 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6826#discussion_r32416442
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112068131
Merged build started.
---
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/6762#issuecomment-112068084
Merged build triggered.
---
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
1 - 100 of 482 matches
Mail list logo
