Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6725#issuecomment-110679637
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/6725#issuecomment-110679595
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/6721#issuecomment-110681938
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/6721#issuecomment-110681921
[Test build #34583 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34583/console)
for PR 6721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6741#issuecomment-110695780
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/6725#issuecomment-110699719
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/6725#issuecomment-110699701
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/6725#issuecomment-110700109
[Test build #34590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34590/consoleFull)
for PR 6725 at commit
Github user Emaasit commented on the pull request:
https://github.com/apache/spark/pull/6668#issuecomment-110702984
@shivaram To create a Spark DataFrame from a local data frame, I used a
subset of the data with fewer rows.
---
If your project is set up for it, you can reply to this
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/6743
[SPARK-6797][SPARKR] Add support for YARN cluster mode.
This PR enables SparkR to dynamically ship the SparkR binary package to the
AM node in YARN cluster mode, thus it is no longer required that
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-110712388
There's a deliberate failing test in this patch, which shows that Jenkins
hasn't been doing the test runs.
I've been using the profile `-Phadoop-2.6
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6737#discussion_r32103529
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -156,6 +156,26 @@ class KMeans private (
this
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6725#issuecomment-110680787
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 a-roberts commented on a diff in the pull request:
https://github.com/apache/spark/pull/6740#discussion_r32104008
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDDOperationScope.scala
---
@@ -95,17 +95,17 @@ private[spark] object RDDOperationScope extends Logging
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6725#issuecomment-110680783
[Test build #34588 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34588/console)
for PR 6725 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6740#issuecomment-110690126
[Test build #34589 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34589/consoleFull)
for PR 6740 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6741#issuecomment-110695759
[Test build #34586 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34586/console)
for PR 6741 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6713#issuecomment-110709432
[Test build #34587 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34587/console)
for PR 6713 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6713#issuecomment-110709481
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/6725#issuecomment-110680237
[Test build #34588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34588/consoleFull)
for PR 6725 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6739#issuecomment-110681513
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6740#discussion_r32104475
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDDOperationScope.scala
---
@@ -95,17 +95,17 @@ private[spark] object RDDOperationScope extends Logging
{
Github user a-roberts commented on the pull request:
https://github.com/apache/spark/pull/6740#issuecomment-110688022
Yep, cheers, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6740#issuecomment-110689317
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/6740#issuecomment-110689246
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/6739
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110700667
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
GitHub user hhbyyh opened a pull request:
https://github.com/apache/spark/pull/6742
[Spark-8169] [ML] Add StopWordsRemover as a transformer
jira: https://issues.apache.org/jira/browse/SPARK-8169
stop words: http://en.wikipedia.org/wiki/Stop_words
StopWordsRemover
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110701410
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/6742#issuecomment-110702491
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/6743#issuecomment-110711890
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 FlytxtRnD commented on a diff in the pull request:
https://github.com/apache/spark/pull/6737#discussion_r32103401
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -156,6 +156,26 @@ class KMeans private (
this
}
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6740#issuecomment-110688654
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 this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6736#issuecomment-110625890
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/6735#issuecomment-110628126
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6716#issuecomment-110628154
LGTM.
---
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/6735#issuecomment-110628109
[Test build #34564 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34564/console)
for PR 6735 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6738#issuecomment-110633479
[Test build #34580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34580/consoleFull)
for PR 6738 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6738#issuecomment-110632994
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/6712#discussion_r32094110
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -1307,16 +1307,9 @@
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/6712#discussion_r32094058
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -1307,16 +1307,9 @@
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6739#issuecomment-110641123
LGTM pending Jenkins.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6730#issuecomment-110643904
[Test build #34571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34571/console)
for PR 6730 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6730#issuecomment-110643942
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/6724#issuecomment-110660184
[Test build #34584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34584/consoleFull)
for PR 6724 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6738#issuecomment-110662643
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/6738#issuecomment-110667197
[Test build #34580 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34580/console)
for PR 6738 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6738#issuecomment-110667218
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6737#discussion_r32102563
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -156,6 +156,26 @@ class KMeans private (
this
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110675165
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6737#discussion_r32102589
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -156,6 +156,26 @@ class KMeans private (
this
}
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110677571
It's because `enclosingObject` in `instantiateClass` is null. The bytecodes
in constructor will check the first field:
```
public
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6736#issuecomment-110625972
[Test build #34575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34575/consoleFull)
for PR 6736 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6736#issuecomment-110625910
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6718#issuecomment-110627870
LGTM other than one 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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6718#discussion_r32093350
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/MathFunctionsSuite.scala
---
@@ -163,6 +163,12 @@ class MathFunctionsSuite
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6718#issuecomment-110627685
[Test build #34578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34578/consoleFull)
for PR 6718 at commit
Github user acidghost commented on the pull request:
https://github.com/apache/spark/pull/3626#issuecomment-110630408
Hello there! I'm interested in reopening this PR and contributing with a
patch to [SPARK-4362] based on this PR with the needed changes. I read [the
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/6739
[SPARK-7886] Added unit test for HAVING aggregate pushdown.
This is a followup to #6712.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6737#issuecomment-110655215
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 a-roberts opened a pull request:
https://github.com/apache/spark/pull/6740
[SPARK-7756] CORE RDDOperationScope fix for IBM Java
IBM Java has an extra method when we do getStackTrace(): this is
getStackTraceImpl, a native method. This causes two tests to fail within
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6718#discussion_r32098163
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/MathFunctionsSuite.scala
---
@@ -163,6 +163,12 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110659227
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/6716#issuecomment-110661369
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/6718#issuecomment-110662646
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/6718#issuecomment-110662640
[Test build #34578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34578/console)
for PR 6718 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6738#issuecomment-110662621
[Test build #34579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34579/console)
for PR 6738 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6713#issuecomment-110672627
[Test build #34587 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34587/consoleFull)
for PR 6713 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6716#issuecomment-110672434
[Test build #34582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34582/console)
for PR 6716 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6727#issuecomment-110672797
LGTM
---
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/6742#issuecomment-110747422
[Test build #34592 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34592/consoleFull)
for PR 6742 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6744#issuecomment-110747848
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/6740#issuecomment-110727757
[Test build #34589 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34589/console)
for PR 6740 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6740#issuecomment-110727810
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 MechCoder opened a pull request:
https://github.com/apache/spark/pull/6744
[SPARK-4127] Python bindings for StreamingLinearRegressionWithSGD
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MechCoder/spark spark-4127
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6744#issuecomment-110746932
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/6744#issuecomment-110747122
[Test build #34596 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34596/consoleFull)
for PR 6744 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6738#discussion_r32110291
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -0,0 +1,198 @@
+/*
+ * Licensed to the Apache Software
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110731067
Heh, well it's supposed to be used when in the `spark-shell` I suppose.
However I agree that it seems to have not been used for a long time,
accidentally.
I
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6723#discussion_r32112388
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/hiveUdfs.scala
---
@@ -81,6 +82,8 @@ private[hive] case class HiveSimpleUdf(funcWrapper:
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6735#discussion_r32113419
--- Diff: core/src/main/scala/org/apache/spark/util/ClosureCleaner.scala ---
@@ -109,7 +109,16 @@ private[spark] object ClosureCleaner extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110740642
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/6744#issuecomment-110743132
cc: @freeman-lab Will remove the LinearDataGenerator stuff (or rebase over
master) as soon as https://github.com/apache/spark/pull/6715 is merged.
---
If your
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6731#issuecomment-110744784
Changed SparkEnv.actorSystem to be a function such that we can use the
deprecated flag with it and added a deprecated message.
I can add `@deprecated` flat to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110747397
[Test build #34591 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34591/consoleFull)
for PR 6724 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110747493
[Test build #34594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34594/consoleFull)
for PR 6735 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6713#issuecomment-110731346
**[Test build #894 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/894/console)**
for PR 6713 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6725#issuecomment-110746800
[Test build #34590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34590/console)
for PR 6725 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6724#issuecomment-110746846
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/6733#issuecomment-110747866
In-memory columnar part looks good. The test failure was because of
timestamp precision change. We can just ignore those two Hive compatibility
test cases.
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-110747698
[Test build #34593 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34593/consoleFull)
for PR 6743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6744#issuecomment-110747841
[Test build #34596 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34596/console)
for PR 6744 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6738#discussion_r32110381
--- Diff:
unsafe/src/main/java/org/apache/spark/unsafe/types/UTF8String.java ---
@@ -0,0 +1,198 @@
+/*
+ * Licensed to the Apache Software
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110725471
The issue is that if a closure is cleaned twice, when cleaning the closure
at the second time, the `$outer` of this closure may have already been set to
`null`. Then
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6735#issuecomment-110739267
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/6735#issuecomment-110746847
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/6742#issuecomment-110746848
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/6743#issuecomment-110746845
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/6735#issuecomment-110746849
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/6725#issuecomment-110746816
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
1 - 100 of 849 matches
Mail list logo
