Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6906#issuecomment-113632377
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/6888#issuecomment-113632390
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/6888#issuecomment-113634088
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/6888#issuecomment-113634060
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/6864#issuecomment-113641248
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/6814#issuecomment-113641669
[Test build #35308 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35308/console)
for PR 6814 at commit
Github user yu-iskw closed the pull request at:
https://github.com/apache/spark/pull/6908
---
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/6908#issuecomment-113643004
We have already implemented `inSet` which is exactly the same as `in`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6799#issuecomment-113647698
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 this
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6759#discussion_r32871144
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTableSupport.scala
---
@@ -313,10 +314,16 @@ private[parquet] class RowWriteSupport
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6759#discussion_r32871309
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTableSupport.scala
---
@@ -313,10 +314,16 @@ private[parquet] class RowWriteSupport
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6759#discussion_r32871889
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTableSupport.scala
---
@@ -313,10 +314,16 @@ private[parquet] class RowWriteSupport
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6909
[SPARK-8498] Add regression test for SPARK-8470
**Summary of the problem in SPARK-8470.** When using `HiveContext` to
create a data frame of a user case class, Spark throws
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6909#issuecomment-113654178
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/6909#issuecomment-113654649
[Test build #35327 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35327/consoleFull)
for PR 6909 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6909#issuecomment-113655489
[Test build #35328 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35328/consoleFull)
for PR 6909 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6909#issuecomment-113655361
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/6883#issuecomment-113660121
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/6883#issuecomment-113660077
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6866#discussion_r32875291
--- Diff: dev/run-tests.py ---
@@ -28,6 +29,241 @@
USER_HOME = os.environ.get(HOME)
+#
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6866#issuecomment-113663625
[Test build #35334 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35334/consoleFull)
for PR 6866 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6889#issuecomment-113663815
Thanks @falaki -- Merging 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 pull request:
https://github.com/apache/spark/pull/6910#issuecomment-113663931
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/6759#issuecomment-113673423
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/6632#issuecomment-113682450
[Test build #35331 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35331/console)
for PR 6632 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6632#issuecomment-113682475
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 yhuai closed the pull request at:
https://github.com/apache/spark/pull/6913
---
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 koeninger commented on the pull request:
https://github.com/apache/spark/pull/6846#issuecomment-113685902
My original pr was against master
On Fri, Jun 19, 2015 at 7:27 PM, Tathagata Das notificati...@github.com
wrote:
Was this committed to
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6913#issuecomment-113685477
Merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6759#issuecomment-113687001
[Test build #35332 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35332/console)
for PR 6759 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6759#issuecomment-113687010
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-113689106
@prabeesh Lets revive this PR.
@zsxwing Since you have already done the Flume Python API in #6830 , could
shepherd this PR?
---
If your project is set up for it, you
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6845#issuecomment-113690421
Can you provide the screenshot of the full UI so that we get sense of the
overall aesthetics?
Also @zsxwing what do you think?
---
If your project is set up for
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/6915
[SQL] [DO NOT MERGE] Use local[*] to launch TestSQLContext and TestHive.
This is just for test. Do not merge it.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5717#issuecomment-113690424
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/5717#issuecomment-113690410
[Test build #35337 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35337/console)
for PR 5717 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6672#discussion_r32880664
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockStatusListener.scala ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6845#issuecomment-113694437
Looks great. In any case it shouldn't overlap with the bars.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6897#issuecomment-113694771
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6915#issuecomment-113695051
[Test build #35343 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35343/console)
for PR 6915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6915#issuecomment-113695053
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/6897#issuecomment-113695040
[Test build #35347 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35347/consoleFull)
for PR 6897 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6632#issuecomment-113695323
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6632
---
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/6791#discussion_r32881156
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/PythonMLLibAPI.scala ---
@@ -465,6 +465,36 @@ private[python] class PythonMLLibAPI extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113710085
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 yhuai opened a pull request:
https://github.com/apache/spark/pull/6913
[HOT-FIX] Fix compilation (caused by
0131142d98b191f6cc112d383aa10582a3ac35bf)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yhuai/spark
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6846#issuecomment-113685150
Was this committed to branch-1.4?
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-113686986
@marmbrus This is the backport.
---
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 yhuai opened a pull request:
https://github.com/apache/spark/pull/6914
[SPARK-8420] [SQL] Fix comparision of timestamps/dates with strings
(branch-1.4)
This is branch 1.4 backport of https://github.com/apache/spark/pull/6888.
Below is the original description.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6897#issuecomment-113690268
[Test build #35342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35342/consoleFull)
for PR 6897 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6672#discussion_r32880590
--- Diff: core/src/main/scala/org/apache/spark/ui/storage/StoragePage.scala
---
@@ -30,11 +30,32 @@ private[ui] class StoragePage(parent: StorageTab)
extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113690721
[Test build #35344 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35344/consoleFull)
for PR 6864 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6672#discussion_r32880575
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/SparkListener.scala ---
@@ -98,6 +99,9 @@ case class SparkListenerExecutorAdded(time: Long,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6759#issuecomment-113690706
[Test build #942 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/942/consoleFull)
for PR 6759 at commit
Github user koeninger commented on the pull request:
https://github.com/apache/spark/pull/6632#issuecomment-113690742
fixed title
---
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 pull request:
https://github.com/apache/spark/pull/6897#issuecomment-113694935
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/6897#issuecomment-113694929
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/3858#issuecomment-113695466
Could you also update the JIRA and title to make it more specific to the
problem? E.g. Python API for ZeroMQ?
On Fri, Jun 19, 2015 at 3:05 PM, industrial-sloth
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6607#discussion_r32881014
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -308,12 +336,25 @@ class ReceiverTracker(ssc:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113696384
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/6864#issuecomment-113696377
[Test build #35344 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35344/console)
for PR 6864 at commit
Github user rnowling commented on the pull request:
https://github.com/apache/spark/pull/3347#issuecomment-113699336
Thanks @andrewor14 !
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/6814#discussion_r32881524
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/Decimal.scala ---
@@ -137,9 +139,9 @@ final class Decimal extends Ordered[Decimal] with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6905#issuecomment-113702249
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/6905#issuecomment-113702266
[Test build #35351 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35351/consoleFull)
for PR 6905 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6905#issuecomment-113702242
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 yu-iskw commented on a diff in the pull request:
https://github.com/apache/spark/pull/6791#discussion_r32882080
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/PythonMLLibAPI.scala ---
@@ -465,6 +465,36 @@ private[python] class PythonMLLibAPI extends
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6917
[SPARK-8496] [Tests] Do not run slow tests for every PR
The purpose of this patch is to speed up the development cycle by
separating slow tests from normal tests. The intention is to run slow
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6863
---
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6912#discussion_r32880332
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/ClientWrapper.scala ---
@@ -136,12 +137,63 @@ private[hive] class ClientWrapper(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-113690075
[Test build #35341 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35341/consoleFull)
for PR 6914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-113690081
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/6915#issuecomment-113690648
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/6864#issuecomment-113690652
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/6915#issuecomment-113690644
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/6864#issuecomment-113690646
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/6911#issuecomment-113691829
[Test build #35346 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35346/consoleFull)
for PR 6911 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-113691835
[Test build #35345 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35345/consoleFull)
for PR 6914 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6905#issuecomment-113695171
@viirya Could you also please document the meaning of the various metrics
in RegressionEvaluator? Users will be surprised that those values are negated.
The doc can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-113700099
[Test build #35349 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35349/consoleFull)
for PR 6830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-113700074
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/6911#issuecomment-113701807
[Test build #35346 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35346/console)
for PR 6911 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6911#issuecomment-113701812
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/6914#issuecomment-113702335
[Test build #35345 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35345/consoleFull)
for PR 6914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-113704494
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/6894#issuecomment-113704530
[Test build #35352 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35352/consoleFull)
for PR 6894 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-113704498
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/6830#issuecomment-113706925
[Test build #35349 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35349/console)
for PR 6830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-113706931
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/6917#issuecomment-113709883
[Test build #35353 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35353/consoleFull)
for PR 6917 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6913#issuecomment-113685378
I am merging it to branch-1.4 to fix compilation.
---
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/6914#issuecomment-113687120
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/6914#issuecomment-113687114
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6910#issuecomment-113689433
Could you please make a separate JIRA and PR for bumping the version. These
are two completely different issues.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6897#issuecomment-113690152
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/6866#issuecomment-113690124
[Test build #35334 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35334/console)
for PR 6866 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6866#issuecomment-113690138
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/6897#issuecomment-113690160
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 maropu closed the pull request at:
https://github.com/apache/spark/pull/3782
---
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
201 - 300 of 1062 matches
Mail list logo