Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053151
Jenkins, retest this please. LGTM pending tests.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1187
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1187#issuecomment-47053084
Thanks merged into master and 1.0.
---
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 n
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1132
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47053018
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 featu
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47052907
Sounds great - I'll merge 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1201
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1204#issuecomment-47052373
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1204#issuecomment-47052374
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16089/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47051689
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47051636
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16083/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47051631
Merged build finished. All automated tests 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47051630
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47051683
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1203#issuecomment-47051633
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47051632
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47051653
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16088/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47051652
Merged build finished. All automated tests 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47051635
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16084/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1203#issuecomment-47051637
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16087/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47051634
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16085/
---
If your project is set up for it, you can
Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/892#issuecomment-47051463
Thanks everybody :-)
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/1205
[SARPK-2263][SQL] Support inserting MAP to Hive tables
JIRA issue: [SPARK-2263](https://issues.apache.org/jira/browse/SPARK-2263)
Map objects were not converted to Hive types before insert
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47051371
The problem is fixed by PR #1201, rebased to the most recent master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47051374
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47051360
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 h
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47051246
LGTM, thanks for fixing 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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47050968
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47050969
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16082/
---
If your project
Github user sebastienrainville commented on a diff in the pull request:
https://github.com/apache/spark/pull/1140#discussion_r14165286
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -206,14 +203,13 @@ private[spark] class
Github user sebastienrainville commented on a diff in the pull request:
https://github.com/apache/spark/pull/1140#discussion_r14165073
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -206,14 +203,13 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47050071
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16081/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47050070
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1204#issuecomment-4705
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1204#issuecomment-47050010
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 have
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1204
Fix possible null pointer in acumulator toString
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark nullPointerToString
Alternativ
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/962#discussion_r14164719
--- Diff: core/src/main/scala/org/apache/spark/executor/TaskMetrics.scala
---
@@ -67,6 +67,12 @@ class TaskMetrics extends Serializable {
var diskByt
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/654#issuecomment-47049345
Just rebased and fixed a unit test that started failing after recent
changes to the test class.
---
If your project is set up for it, you can reply to this email and have
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/1163#discussion_r14164580
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -67,73 +62,72 @@ case class HashJoin(
@transient lazy val st
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47048883
I think the `CachedTableSuite` failed because `TestData` was not properly
initialized. Is it related to running test cases in parallel?
---
If your project is set up f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47048849
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1203#issuecomment-47048840
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1203#issuecomment-47048848
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47048842
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 ha
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47048795
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1203#discussion_r14164404
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/ExecutorRunner.scala ---
@@ -87,9 +88,9 @@ private[spark] class ExecutorRunner(
if
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47048769
Hey There,
This code is actually pretty dense - so great job finding this bug! I've
created a separate JIRA to clean up this code a bit.
WRT your fix. I
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1203#discussion_r14164394
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/ui/LogPage.scala ---
@@ -120,7 +120,7 @@ private[spark] class LogPage(parent: WorkerWebUI)
ex
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1203#discussion_r14164385
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/ui/LogPage.scala ---
@@ -120,7 +120,7 @@ private[spark] class LogPage(parent: WorkerWebUI)
ex
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/1203
[SPARK-2258 / 2266] Fix a few worker UI bugs
**SPARK-2258.** Worker UI displays zombie processes if the executor throws
an exception before a process is launched. This is because we only inform t
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1147#issuecomment-47048555
BTW, it will be cool if #1163 is merged before I start working on this
updating.
---
If your project is set up for it, you can reply to this email and have your
r
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1140#discussion_r14164279
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -206,14 +203,13 @@ private[spark] class MesosSched
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47048152
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47048154
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16079/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47048155
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16080/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47048153
Merged build finished.
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1147#issuecomment-47047912
I am planning to split the PR into 3 smaller ones, 2 of those (#1187 &
#1190) are done , and I will update this PR as the 3rd one once the previous
have been merge
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1063#issuecomment-47047248
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1063#issuecomment-47047249
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16086/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1063#issuecomment-47047148
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47047147
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1063#issuecomment-47047141
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47047140
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 h
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1202
[SPARK-2267] Log exception when TaskResultGetter fails to fetch/deserialze
task result
Note that this is only for branch-1.0 because master's been fixed.
You can merge this pull request into a Git re
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47046507
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47046500
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 ha
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1140#discussion_r14163153
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -206,14 +203,13 @@ private[spark] class MesosSched
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47046244
Ok this is now up to date and good for you to review @andrewor14
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045857
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045868
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 have
Github user concretevitamin commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045612
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1198
---
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 enab
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1198#issuecomment-47045522
I merged this into 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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1198#issuecomment-47045420
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045426
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16075/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1198#issuecomment-47045427
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16076/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045423
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1132#issuecomment-47045421
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47045422
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1132#issuecomment-47045424
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16077/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47045425
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16078/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045181
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47045191
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 have
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-47044140
Let me know if there is anything I can do to help.
On Jun 24, 2014 6:33 PM, "Tathagata Das" wrote:
> This is a weird binary compatibility check failure, that
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-47044062
This is a weird binary compatibility check failure, that should not be
thrown. We are looking at our end for fixing this and rerunning the tests. Once
this is figured out, I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47042486
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47042499
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 have
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47042376
@pwendell I was just trying to avoid doing a bunch more updates to this.
I've pushed the rebased version and the new Json tests but I don't think the
new tests will
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47042143
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16074/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1163#issuecomment-47042142
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47041748
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47041740
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47041534
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16073/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47041533
Merged build finished.
---
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 hav
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47041465
/cc @liancheng
---
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/1201#issuecomment-47041365
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1201#issuecomment-47041354
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 h
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1201
[SPARK-2264][SQL] Fix failing CachedTableSuite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark fixCacheTests
Alternatively you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47041026
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47041008
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 h
101 - 200 of 363 matches
Mail list logo
