Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46891714
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16034/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/892#issuecomment-46891709
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/1050#issuecomment-46891717
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16035/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46891711
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/1183#issuecomment-46891625
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16033/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46891623
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/1159#issuecomment-46891627
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16032/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46891621
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 YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-46890516
Thanks a lot,Michael .I have update the code .I don't know if all the
files are right? Can these files be merged ?Thanks.a lot!
---
If your project is set up for it,
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46887083
Sorry about this and thanks for fixing it @andrewor14 ! Just one change --
I think you should also delete proc.stderr.readLines() on line 57, since that
won't retu
Github user hsaputra commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46885170
Just push changes to fix Scalastyle checks for over 100 char in a line.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46885185
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/1185#issuecomment-46885180
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46885198
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1179#discussion_r14092359
--- Diff: repl/src/main/scala/org/apache/spark/repl/SparkImports.scala ---
@@ -182,15 +182,26 @@ trait SparkImports {
// ambiguity errors will no
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/892#issuecomment-46884580
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/892#issuecomment-46884592
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 mattf opened a pull request:
https://github.com/apache/spark/pull/1185
Autodetect JAVA_HOME on RPM-based systems
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf/spark master-1
Alternatively you can review and a
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/892#issuecomment-46884029
Jenkins, this is ok to test
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1182#issuecomment-46883069
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16031/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1181
---
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/1182#issuecomment-46883068
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1181#issuecomment-46882554
Thanks - I'm merging this into master and branch 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 y
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-46881013
So the problem where everything becomes the same row is due to a
performance optimization that we make in Spark SQL. Most operators actually
only allocate a single row
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1184#issuecomment-46880938
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/1184#issuecomment-46880924
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 kellrott opened a pull request:
https://github.com/apache/spark/pull/1184
Make the createModel method from GeneralizedLinearAlgorithm public
Making the createModel from the GeneralizedLinearAlgorithm trait user
accessible.
You can merge this pull request into a Git repo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879650
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/1050#issuecomment-46879669
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/1183
[SPARK-1669][SQL] Made cacheTable idempotent
JIRA issue: [SPARK-1669](https://issues.apache.org/jira/browse/SPARK-1669)
Caching the same multiple times should end up with only 1 in-memory
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879668
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/1183#issuecomment-46879649
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 the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879165
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879005
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/1183#issuecomment-46879021
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/1182#issuecomment-46877098
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/1159#issuecomment-46877113
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/1182#issuecomment-46877112
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/1159#issuecomment-46877100
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 kellrott opened a pull request:
https://github.com/apache/spark/pull/1182
Fix for SPARK-2228
Add check to see if stageId exists in stageIdToPool before attempting to
remove it from poolToActiveStages.
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46873730
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16030/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46873729
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 SpyderRiverA commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-46871874
:+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
enab
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1094#issuecomment-46869006
@rahulsinghaliitd that bug is about linking to the running web ui of the
driver in yarn-client mode. Slightly different than this one, which is about
setting the link afte
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46868383
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/1112#issuecomment-46868364
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/1159#issuecomment-46867542
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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46867543
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16029/
---
If your project
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46865956
not sure if i am supposed to deal with these failures?
On Sat, Jun 21, 2014 at 1:52 PM, UCB AMPLab
wrote:
> Refer to this link for build res
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46864496
thanks for the review. If you have better verbage to use in in the docs
let me know. I need to rebase this to latest master too, which I'll do shortly.
---
If your p
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1158
---
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14081769
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class YarnClie
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46861993
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/1159#issuecomment-46861976
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 willb commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-46860741
Can someone take another look at this PR?
---
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 doe
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080567
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/** Ad
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080360
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/*
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080191
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -244,6 +247,9 @@ class CoarseGrainedSchedulerBa
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14079754
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class Yarn
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14079223
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Application
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46855913
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/1050#issuecomment-46855914
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16028/
---
If your project is set up for it, you can
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14078643
--- Diff: core/src/main/scala/org/apache/spark/ui/WebUI.scala ---
@@ -43,7 +43,7 @@ private[spark] abstract class WebUI(
extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46854533
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/1180#issuecomment-46854534
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16027/
---
If your project
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14078350
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class Yarn
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077980
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/** Ad
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46852803
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16025/
---
If your project
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077908
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Application
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46852802
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077844
--- Diff: core/src/main/scala/org/apache/spark/ui/UIUtils.scala ---
@@ -135,7 +135,16 @@ private[spark] object UIUtils extends Logging {
}
//
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077679
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/*
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077685
--- Diff: core/src/main/scala/org/apache/spark/ui/UIUtils.scala ---
@@ -135,7 +135,16 @@ private[spark] object UIUtils extends Logging {
}
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077635
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Application
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46850760
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/1180#issuecomment-46850763
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16024/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1181#issuecomment-46850232
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46850235
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/1050#issuecomment-46850255
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 mattf opened a pull request:
https://github.com/apache/spark/pull/1181
Fix mvn detection
When mvn is not detected (not in executor's path), 'set -e' causes the
detection to terminate the script before the helpful error message can
be displayed.
You can merge this
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849805
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 h
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849779
I just checked it merges cleanly and still these test failures.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46848936
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/1050#issuecomment-46848937
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16026/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46847666
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/1180#issuecomment-46848339
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/1180#issuecomment-46848316
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/1050#issuecomment-46847651
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/560
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/560#issuecomment-46847166
+1 looks good, thanks @vanzin.
---
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/1068#issuecomment-46847077
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/1068#issuecomment-46847056
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/1180#issuecomment-46845280
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/1180#issuecomment-46845264
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 witgo opened a pull request:
https://github.com/apache/spark/pull/1180
[WIP]Spark 2037: yarn client mode doesn't support
spark.yarn.max.executor.failures
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SP
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46841282
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16023/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46841280
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/1179#issuecomment-46836628
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/1179#issuecomment-46836615
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/1179#issuecomment-46833245
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
101 - 200 of 227 matches
Mail list logo
