Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13301#issuecomment-221696827
**[Test build #59292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59292/consoleFull)**
for PR 13301 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12943#issuecomment-221696163
So I simplified the test down a fair amount, didn't switch to printing the
model weights since that seems like it could be flaky with floats (I can of
course use ...
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13270#discussion_r64645557
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -68,7 +69,8 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13301#issuecomment-221692709
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/13301#issuecomment-221692715
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13301#issuecomment-221692582
**[Test build #59291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59291/consoleFull)**
for PR 13301 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13301#issuecomment-221690057
**[Test build #59291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59291/consoleFull)**
for PR 13301 at commit
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/13301
[SPARK-15449][MLlib][Example]:Wrong Data Format - Documentation Issue
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
In the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12943#issuecomment-221686698
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/13272#issuecomment-221686186
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221685732
**[Test build #59284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59284/consoleFull)**
for PR 13272 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12943#issuecomment-221686538
**[Test build #59290 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59290/consoleFull)**
for PR 12943 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221686181
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/12943#issuecomment-221686699
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13267
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221684412
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/13266#issuecomment-221682051
**[Test build #59289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59289/consoleFull)**
for PR 13266 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221685313
**[Test build #3019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3019/consoleFull)**
for PR 13299 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13267#issuecomment-221684056
Thanks - merging in master/2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221684272
**[Test build #59289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59289/consoleFull)**
for PR 13266 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221684417
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12943#issuecomment-221683374
**[Test build #59290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59290/consoleFull)**
for PR 12943 at commit
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221681098
@MLnick Done. 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221680302
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 xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/13276#issuecomment-221680340
Adding to the above observation:
1. `LIST FILES` command output is not captured on all
`spark-branch-2.0-test-*` jenkins jobs.
2. `LIST FILE
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221680304
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-22167
**[Test build #59286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59286/consoleFull)**
for PR 13299 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221677507
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221677309
**[Test build #59285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59285/consoleFull)**
for PR 13271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221677504
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/9192#issuecomment-221676892
Thanks @felixcheung for the update. I left some minor comments inline.
It seems unfortunate that we need to do some amount of code duplication to
get this to
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/9192#discussion_r64633002
--- Diff: R/pkg/R/SQLContext.R ---
@@ -37,6 +37,37 @@ getInternalType <- function(x) {
stop(paste("Unsupported type for SparkDataFrame:",
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221675752
Confirmed `build/sbt package` works and the plugin dep resolves.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/9192#discussion_r64633530
--- Diff: R/pkg/inst/tests/testthat/test_sparkSQL.R ---
@@ -169,48 +169,50 @@ test_that("create DataFrame from RDD", {
error = function(err) {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13261
---
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/9192#discussion_r64633209
--- Diff: R/pkg/R/SQLContext.R ---
@@ -254,6 +301,7 @@ jsonFile <- function(sqlContext, path) {
#' df <- jsonRDD(sqlContext, rdd)
#'}
+#
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13261#issuecomment-221673769
Thanks, merging to master and 2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221672349
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/13271#issuecomment-221672353
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221672103
**[Test build #59283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59283/consoleFull)**
for PR 13271 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64631597
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -108,21 +108,20 @@ case class DataSource(
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/13295#issuecomment-221670088
Jenkins, 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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64631743
--- Diff: python/pyspark/sql/utils.py ---
@@ -77,6 +83,8 @@ def deco(*a, **kw):
raise QueryExecutionException(s.split(': ', 1)[1],
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12836#issuecomment-221669659
Hmm - What is the difference between `dapply_row` and SQL row UDF ? anyways
this discussion probably belongs in a new JIRA and not in this PR
---
If your project is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13295#issuecomment-221671264
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/13295#issuecomment-221671233
**[Test build #59288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59288/consoleFull)**
for PR 13295 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/13295#issuecomment-221670324
Thanks @mhnatiuk for opening this PR. Could we also add a unit test in
`test_sparkSQL.R` for this ?
---
If your project is set up for it, you can reply to this
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221669383
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64631435
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -108,21 +108,20 @@ case class DataSource(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13295#issuecomment-221671267
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221670964
@MLnick Sure. I will do it soon. Now, I am debugging a R bug. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13295#issuecomment-221671259
**[Test build #59288 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59288/consoleFull)**
for PR 13295 at commit
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221668874
@shivaram I am debugging and try to find a hint.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12004#issuecomment-221668693
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/12004#issuecomment-221668685
**[Test build #59287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59287/consoleFull)**
for PR 12004 at commit
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/13277#issuecomment-221668407
Merged to master/branch-2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12004#issuecomment-221668697
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13277
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12004#issuecomment-221668290
**[Test build #59287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59287/consoleFull)**
for PR 12004 at commit
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/13266#issuecomment-221668080
@wangmiao1981 could you do the same for the `OneVsRestExample`? ie remove
`DataFrame` type annotation and import. You can do that in this PR.
---
If your project is
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/13283#issuecomment-221665525
@gatorsmile I saw it reports `org.apache.spark.sql.AnalysisException:
Failed to find data source: mydatabase. Please find packages at
http://spark-packages.org;; line
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13298#issuecomment-22145
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13298#issuecomment-221666300
**[Test build #59281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59281/consoleFull)**
for PR 13298 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13298#issuecomment-22144
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/13165#discussion_r64628244
--- Diff: R/pkg/R/client.R ---
@@ -60,6 +60,15 @@ generateSparkSubmitArgs <- function(args, sparkHome,
jars, sparkSubmitOpts, pack
combinedArgs
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64626689
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -132,12 +131,11 @@ case class DataSource(
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221663730
@wangmiao1981 Lets continue the pipeRDD debugging on the JIRA. This change
LGTM for the subset and the masking tests
@felixcheung any other comments ?
---
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/13283#issuecomment-221662515
> ISSUE 3: Unable to detect incompatibility libraries for Spark 2.0 in Data
Source Resolution. We report a strange error message:
> SQL Example:
> select id
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/13300#issuecomment-221661115
@HyukjinKwon @falaki Could you review the PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64622938
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -132,12 +131,11 @@ case class DataSource(
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64622417
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -132,12 +131,11 @@ case class DataSource(
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221656579
Re-tested on Ubuntu, the pipedRDD test case still fails. R version 3.3.0
beta (2016-03-30 r70404)
---
If your project is set up for it, you can reply to this
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13294#issuecomment-221656682
Thank you, @andrewor14 and @srowen !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13298
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13294
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13298#issuecomment-221654254
OK, merging into master 2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13300#issuecomment-221654079
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13289
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13294#issuecomment-221653771
m2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13289#discussion_r64620005
--- Diff: python/pyspark/sql/session.py ---
@@ -138,24 +138,37 @@ def getOrCreate(self):
"""Gets an existing :class:`SparkSession` or, if
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13160
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13289#issuecomment-221653189
Looks good. Merging into master 2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user xwu0226 opened a pull request:
https://github.com/apache/spark/pull/13300
[SPARK-15463][SQL] support creating dataframe out of RDD[String] for csv
data
## What changes were proposed in this pull request?
Currently only `DataFrameReader.json(rdd: RDD[String]):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13160#issuecomment-221652457
LGTM2. Merging into master 2.0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221651230
cc @rxin @MLnick @vanzin (could you take a look at the build)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13299#issuecomment-221651306
**[Test build #59286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59286/consoleFull)**
for PR 13299 at commit
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/13299
[SPARK-15525][SQL][BUILD] Upgrade ANTLR4 SBT plugin
## What changes were proposed in this pull request?
The ANTLR4 SBT plugin has been moved from its own repo to one on bintray.
The version
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221649899
**[Test build #59285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59285/consoleFull)**
for PR 13271 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221645693
**[Test build #59284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59284/consoleFull)**
for PR 13272 at commit
Github user clockfly commented on a diff in the pull request:
https://github.com/apache/spark/pull/13269#discussion_r64617059
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/KeyValueGroupedDataset.scala ---
@@ -42,17 +42,9 @@ class KeyValueGroupedDataset[K, V] private[sql](
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13264
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/13264#issuecomment-221646004
LGTM. Merging to master / 2.0. 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/13292
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221644960
@JoshRosen @srowen this is ready for review now, you can check the failed
builds to see that it's working.
---
If your project is set up for it, you can reply to this
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/13292#issuecomment-221644166
merging to master & 2.0 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13297#issuecomment-221643566
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13297#issuecomment-221643563
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/13297#issuecomment-221643262
**[Test build #59280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59280/consoleFull)**
for PR 13297 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221641642
**[Test build #59283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59283/consoleFull)**
for PR 13271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221641404
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
401 - 500 of 685 matches
Mail list logo
