Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-157638387
**[Test build #46193 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46193/consoleFull)**
for PR 9488 at commit
[`dd3fd8a`](https://gith
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-157638100
Updated with master, thanks guys!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9783
---
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/9706#issuecomment-157635698
What's the status on 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 have th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157634937
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157634928
**[Test build #46190 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46190/consoleFull)**
for PR 9798 at commit
[`3ea051a`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157634940
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9783#issuecomment-157634917
I've merged 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 have this featur
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45169071
--- Diff: core/src/main/scala/org/apache/spark/rdd/SqlNewHadoopRDD.scala ---
@@ -95,6 +95,8 @@ private[spark] class SqlNewHadoopRDD[V: ClassTag](
}
Github user somideshmukh commented on the pull request:
https://github.com/apache/spark/pull/9733#issuecomment-157634620
I have push new commit to SomilBranch-1.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
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45169104
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+ * Li
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9799#issuecomment-157634456
**[Test build #46191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46191/consoleFull)**
for PR 9799 at commit
[`907ec97`](https://gith
Github user choochootrain commented on a diff in the pull request:
https://github.com/apache/spark/pull/9779#discussion_r45168978
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskResultGetterSuite.scala ---
@@ -119,5 +123,66 @@ class TaskResultGetterSuite extends SparkF
Github user choochootrain commented on a diff in the pull request:
https://github.com/apache/spark/pull/9779#discussion_r45168868
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskResultGetterSuite.scala ---
@@ -119,5 +123,66 @@ class TaskResultGetterSuite extends SparkF
Github user choochootrain commented on a diff in the pull request:
https://github.com/apache/spark/pull/9779#discussion_r45168854
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskResultGetterSuite.scala ---
@@ -119,5 +123,66 @@ class TaskResultGetterSuite extends SparkF
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157634102
**[Test build #46190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46190/consoleFull)**
for PR 9798 at commit
[`3ea051a`](https://gith
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9788#discussion_r45168848
--- Diff: core/src/main/scala/org/apache/spark/util/SizeEstimator.scala ---
@@ -32,6 +32,16 @@ import org.apache.spark.annotation.DeveloperApi
import org.a
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9716
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/9799
[SPARK-11792] remove blockManager from BytesToBytesMap
BytesToBytesMap will be used by UnsafeHashRelation, and stored in memory
store, then SizeEstimator will see BlockManager as part of BytesToBytes
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9716#issuecomment-157633974
Merged into master and branch-1.6. 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
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9798#discussion_r45168631
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/StandardScalerSuite.scala ---
@@ -56,23 +60,29 @@ class StandardScalerSuite extends SparkFunSuite wi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157633520
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157633322
**[Test build #46188 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46188/consoleFull)**
for PR 9785 at commit
[`46b2a6e`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157633522
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/9798
[SPARK-6787] [ML] add read/write to estimators under ml.feature (1)
Add read/write support to the following estimators under spark.ml:
* CountVectorizer
* IDF
* MinMaxScaler
* Sta
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9791#discussion_r45168252
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -26,6 +26,7 @@
from pyspark.rdd import ignore_unicode_prefix
from pyspark.sql.column import _to_seq
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9791#discussion_r45168270
--- Diff: python/pyspark/sql/utils.py ---
@@ -71,3 +71,10 @@ def install_exception_handler():
patched = capture_sql_exception(original)
# only
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157631978
I fixed subset, lag, and filter. Not sure about the rest:
```
cov(x, y = NULL, use = "everything",
method = c("pearson", "kendall", "spearm
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157631673
There are still some network related code that's going into 1.6 (one is the
config naming thing). I'm concerned they might conflict. Maybe you can just
submit more prs basi
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9791#issuecomment-157631517
cc @davies
---
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
enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157631502
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157631500
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157631431
**[Test build #46161 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46161/consoleFull)**
for PR 9780 at commit
[`a645c11`](https://git
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9788#discussion_r45167423
--- Diff: core/src/main/scala/org/apache/spark/util/SizeEstimator.scala ---
@@ -32,6 +32,16 @@ import org.apache.spark.annotation.DeveloperApi
import org.apa
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/9680#discussion_r45167221
--- Diff: R/pkg/R/functions.R ---
@@ -259,6 +259,20 @@ setMethod("column",
function(x) {
col(x)
})
+#' corr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9797#issuecomment-157630979
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 pr
GitHub user mortada opened a pull request:
https://github.com/apache/spark/pull/9797
python3 compatibility for launching ec2 m3 instances
this currently breaks for python3 because `string` module doesn't have
`letters` anymore, instead `ascii_letters` should be used
You can merge
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9788#discussion_r45166982
--- Diff: core/src/main/scala/org/apache/spark/util/SizeEstimator.scala ---
@@ -32,6 +32,16 @@ import org.apache.spark.annotation.DeveloperApi
import org.a
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/9680#discussion_r45166927
--- Diff: R/pkg/R/functions.R ---
@@ -259,6 +259,21 @@ setMethod("column",
function(x) {
col(x)
})
+#' corr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157630539
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157630538
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157630526
**[Test build #46189 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46189/consoleFull)**
for PR 9790 at commit
[`2ba4114`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157630136
**[Test build #46188 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46188/consoleFull)**
for PR 9785 at commit
[`46b2a6e`](https://gith
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157630046
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 a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9796#issuecomment-157629478
**[Test build #46187 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46187/consoleFull)**
for PR 9796 at commit
[`0d8e6c1`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157629414
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 project
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9788#discussion_r45166467
--- Diff: core/src/main/scala/org/apache/spark/util/SizeEstimator.scala ---
@@ -32,6 +32,16 @@ import org.apache.spark.annotation.DeveloperApi
import org.ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157629416
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user vikasnp commented on the pull request:
https://github.com/apache/spark/pull/9689#issuecomment-157629142
@yinxusen I've fixed the issues you've pointed out.
scala-style and python-style tests were successful.
Please let me know if more changes are required. I'll be
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9701
---
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/9790#discussion_r45166324
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/util/WriteAheadLogSuite.scala
---
@@ -508,14 +509,17 @@ class BatchedWriteAheadLogSuite extends
C
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9796#issuecomment-157628895
**[Test build #46186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46186/consoleFull)**
for PR 9796 at commit
[`589083b`](https://gith
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9701#discussion_r45166255
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -381,8 +393,12 @@ object DateTimeUtils {
}
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9770#discussion_r45166023
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -1063,6 +1065,34 @@ class Analyzer(
Project(p.
GitHub user GraceH opened a pull request:
https://github.com/apache/spark/pull/9796
Return "false" is nothing to kill in killExecutors
In discussion (SPARK-9552), we proposed a force kill in `killExecutors`.
But if there is nothing to kill, it will return back with true
(acknowledg
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157627588
**[Test build #46185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46185/consoleFull)**
for PR 9481 at commit
[`84b7a42`](https://gith
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9788#discussion_r45165606
--- Diff: core/src/main/scala/org/apache/spark/util/SizeEstimator.scala ---
@@ -32,6 +32,16 @@ import org.apache.spark.annotation.DeveloperApi
import org.a
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6665#issuecomment-157627304
Merged into master and branch-1.6. 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6665
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157627070
> What's going on with jenkins?
Forgot to merge master. Some new commits to master needs to be updated as
well.
---
If your project is set up for it, you can r
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157626868
@tdas Addressed
---
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/9770#issuecomment-157626801
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9770#issuecomment-157626798
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9770#issuecomment-157626716
**[Test build #46171 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46171/consoleFull)**
for PR 9770 at commit
[`f9c38cf`](https://git
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/9709#issuecomment-157626540
So if I understand the change correctly this will treat null values the
same as the string "null" yes? If we do this we should document that behavior
(it seems like a re
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157625965
**[Test build #46183 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46183/consoleFull)**
for PR 9795 at commit
[`3f5559b`](https://gith
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157625901
I didn't know about ArgumentCaptors. My custom matcher was practically
going to do the same thing. It might be cleaner and even less fragile hopefully
---
If your projec
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9741
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157624452
**[Test build #2084 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2084/consoleFull)**
for PR 9481 at commit
[`3fd22e1`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157624447
**[Test build #46182 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46182/consoleFull)**
for PR 8760 at commit
[`1df57fb`](https://gith
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157624013
I am merging this to master and 1.6. Thanks @tedyu!
---
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/9481#issuecomment-157623456
What's going on with 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 tdas commented on the pull request:
https://github.com/apache/spark/pull/9790#issuecomment-157622191
Rather than enforcing ordering, isn it cleaner to capture the passed
arguments to `wal.write`, deserialize and compare as sets?
Its cleaner because the unit test should
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157622094
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157622091
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157621597
**[Test build #46172 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46172/consoleFull)**
for PR 9481 at commit
[`3fd22e1`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9787#issuecomment-157620868
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9787#issuecomment-157620869
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9787#issuecomment-157620757
**[Test build #46170 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46170/consoleFull)**
for PR 9787 at commit
[`9c3bd92`](https://git
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/9795
[SPARK-11809] Switch the default Mesos mode to coarse-grained mode
Based on my conversions with people, I believe the consensus is that the
coarse-grained mode is more stable and easier to reason about
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157620327
cc @andrewor14 @tnachen @dragos
---
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/9794#issuecomment-157620031
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 pr
GitHub user HuJiayin opened a pull request:
https://github.com/apache/spark/pull/9794
[SPARK-4036]Add Conditional Random Fields (CRF) algorithm to Spark MLlib
Conditional random fields (CRFs) are a class of statistical modelling
method often applied in pattern recognition and machin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157617386
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157617390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157617380
**[Test build #46181 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46181/consoleFull)**
for PR 8760 at commit
[`fe6abe7`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157616110
**[Test build #46181 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46181/consoleFull)**
for PR 8760 at commit
[`fe6abe7`](https://gith
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-157616063
I think adding to JavaDStreamLike is okay. No one I imagine extends
JavaDStreamLike.
@BryanCutler please update the PR soon :)
---
If your project is set up for it,
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9769#issuecomment-157614027
Ok thanks for the clarification. It might take me a couple of days to get
to this as the change looks a bit involved.
cc @felixcheung
---
If your project is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9732
---
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/8760#issuecomment-157613541
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 project
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9732#issuecomment-157613566
Merging this to master, branch-1.6
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613529
**[Test build #46180 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46180/consoleFull)**
for PR 8760 at commit
[`c6bfba2`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613542
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9789#issuecomment-157613505
**[Test build #46179 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46179/consoleFull)**
for PR 9789 at commit
[`765c7e6`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613279
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613224
**[Test build #46180 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46180/consoleFull)**
for PR 8760 at commit
[`c6bfba2`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613288
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157613265
**[Test build #46177 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46177/consoleFull)**
for PR 8760 at commit
[`c6bfba2`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9793#issuecomment-157613131
**[Test build #46178 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46178/consoleFull)**
for PR 9793 at commit
[`b69c1ee`](https://gith
1 - 100 of 942 matches
Mail list logo
