Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-55040407
Merging in master. 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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-55040214
+1
---
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 w
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-55024120
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20049/consoleFull)
for PR 2331 at commit
[`44c1e76`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-55015566
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20049/consoleFull)
for PR 2331 at commit
[`44c1e76`](https://github.com/ap
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-55009770
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 not have th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-54946353
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20032/consoleFull)
for PR 2331 at commit
[`44c1e76`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2331#issuecomment-54941044
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20032/consoleFull)
for PR 2331 at commit
[`44c1e76`](https://github.com/ap
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/2331
Minor - Fix trivial compilation warnings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1 compilation-warn
Alternatively
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2255
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2255#issuecomment-54386435
This failed an unrelated test. I'm 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 you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2255#issuecomment-54386342
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19700/consoleFull)
for PR 2255 at commit
[`1fbdfe9`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2255#issuecomment-54380828
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19700/consoleFull)
for PR 2255 at commit
[`1fbdfe9`](https://github.com/ap
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2255#issuecomment-54380534
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 fea
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2255#issuecomment-54376924
Maybe use 1.2.0-SNAPSHOT instead?
---
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/2255
[Minor] Fix outdated Spark version
This is causing the event logs to include a file called
SPARK_VERSION_1.0.0, which is not accurate.
You can merge this pull request into a Git repository by ru
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2105
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2105#issuecomment-53158982
I merged this; 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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2105#issuecomment-53156760
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 pro
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/2105
[Minor] fix typo
Fix a typo in comment.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 fix_typo
Alternatively you can review and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1105
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46527438
Thanks, merged 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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46479086
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/1105#issuecomment-46479087
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15877/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46474141
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/1105#issuecomment-46474119
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46473996
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 WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46437289
Updated.
---
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 featur
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1105#discussion_r13903361
--- Diff: core/src/main/scala/org/apache/spark/util/MetadataCleaner.scala
---
@@ -91,8 +91,13 @@ private[spark] object MetadataCleaner {
conf.set(Metada
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46317911
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 pro
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/1105
Minor fix
The value "env" is never used in SparkContext.scala.
Add detailed comment for method setDelaySeconds in MetadataCleaner.scala
instead of the unsure one.
You can merge t
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1097
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1097#issuecomment-46251700
Thanks. I'm merging this one. The test that failed was a flume test that is
sometimes flaky.
---
If your project is set up for it, you can reply to this email and have you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1097#issuecomment-46251255
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/1097#issuecomment-46251256
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15825/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1097#issuecomment-46244984
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/1097#issuecomment-46244993
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/1097
Minor fix: made "EXPLAIN" output to play well with JDBC output format
Fixed the broken JDBC output. Test from Shark `beeline`:
```
beeline> !connect jdbc:hive2://localhost:1/
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1058
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45972976
Thanks - I did another pass - looks good.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45959116
This is ready for merge from my side. Any other comments?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45958124
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15728/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45958121
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/1058#issuecomment-45954695
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/1058#issuecomment-45954678
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13729334
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -329,15 +326,16 @@ private[spark] class BlockManager(
* never dele
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13728921
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -329,15 +326,16 @@ private[spark] class BlockManager(
* never dele
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13728860
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -637,76 +633,63 @@ private[spark] class BlockManager(
// If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45952769
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15722/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45952767
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45951390
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15720/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45951388
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 this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13727924
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -637,76 +633,63 @@ private[spark] class BlockManager(
// If w
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726891
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -329,15 +326,16 @@ private[spark] class BlockManager(
* never delete
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45948846
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15719/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45948845
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 this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726465
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -24,6 +24,8 @@ import scala.collection.mutable.ArrayBuffer
import o
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726230
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -353,7 +351,7 @@ private[spark] class BlockManager(
case Some
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726181
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -782,15 +765,16 @@ private[spark] class BlockManager(
for (peer: Bl
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726187
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -329,15 +326,16 @@ private[spark] class BlockManager(
* never dele
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726163
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -750,19 +736,16 @@ private[spark] class BlockManager(
byt
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726037
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -750,19 +736,16 @@ private[spark] class BlockManager(
bytes
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13726015
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -750,19 +736,16 @@ private[spark] class BlockManager(
bytes
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13725590
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -353,7 +351,7 @@ private[spark] class BlockManager(
case Some(b
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13725473
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -329,15 +326,16 @@ private[spark] class BlockManager(
* never delete
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13724792
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -637,76 +633,63 @@ private[spark] class BlockManager(
// If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45944084
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45944076
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 have thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45942352
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45942338
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 have thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45940238
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45940221
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 have thi
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13712498
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -28,46 +28,48 @@ import scala.util.Random
import akka.actor.{ActorSys
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13712333
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -28,46 +28,48 @@ import scala.util.Random
import akka.actor.{ActorSyste
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45840606
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/1058#issuecomment-45840608
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15704/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45836147
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/1058#issuecomment-45836138
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/1058#issuecomment-45821958
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/1058#issuecomment-45821960
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15698/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45819660
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/1058#issuecomment-45819648
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13683529
--- Diff: core/src/main/scala/org/apache/spark/CacheManager.scala ---
@@ -98,7 +102,7 @@ private[spark] class CacheManager(blockManager:
BlockManager) exte
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1058#discussion_r13683274
--- Diff: core/src/main/scala/org/apache/spark/CacheManager.scala ---
@@ -98,7 +102,7 @@ private[spark] class CacheManager(blockManager:
BlockManager) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45818738
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15695/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45818737
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/1058#issuecomment-45816347
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/1058#issuecomment-45816334
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/1058#issuecomment-45816339
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15692/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1058#issuecomment-45816336
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/1058#issuecomment-45812652
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/1058#issuecomment-45812644
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/1058
[Minor] Fix style, formatting and naming in BlockManager etc.
This is a pre-cursor to a bigger change. I wanted to separate out the
relatively insignificant changes so the ultimate PR is not infl
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/970
---
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 enabl
GitHub user ankurdave opened a pull request:
https://github.com/apache/spark/pull/970
Minor: Fix documentation error from apache/spark#946
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ankurdave/spark SPARK-1991_docfix
Alterna
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/585
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/585#issuecomment-41648969
Thanks, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/585#issuecomment-41634044
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14548/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/585#issuecomment-41634041
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/585#issuecomment-41630772
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/585#issuecomment-41630776
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
301 - 400 of 401 matches
Mail list logo
