Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10527#issuecomment-183633038
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/10527#issuecomment-183633037
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/11121#issuecomment-183633448
**[Test build #51234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51234/consoleFull)**
for PR 11121 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183633594
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/11121#issuecomment-183633593
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/11148#issuecomment-183633800
**[Test build #51236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51236/consoleFull)**
for PR 11148 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183633862
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/11148#issuecomment-183633861
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 hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/11078#issuecomment-183636091
Thanks for the review. I tested the change and the max memory dropped from
2.2G to 2G as observed from JConsole. I'll make a new benchmark and post the
details here.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183640804
**[Test build #51237 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51237/consoleFull)**
for PR 10539 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183640947
Test FAILed.
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/10539#issuecomment-183640946
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/11182#issuecomment-183641277
**[Test build #51238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51238/consoleFull)**
for PR 11182 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11182#issuecomment-183641314
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/11182#issuecomment-183641315
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/11181#issuecomment-183642869
**[Test build #51231 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51231/consoleFull)**
for PR 11181 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11181#issuecomment-183643302
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/11181#issuecomment-183643303
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183643331
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183645455
**[Test build #51240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51240/consoleFull)**
for PR 10539 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11180#issuecomment-183645806
Aha, one significant update. Yes, the change here is a good one, as I also
had to install this gem to build the docs. In fact we can simplify:
```
sudo gem
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11180#issuecomment-183648166
I fixed the ASF site at http://spark.apache.org/examples.html and indeed it
required the same gem to be installed to work. So this is related.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183654840
**[Test build #51240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51240/consoleFull)**
for PR 10539 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183654872
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/10539#issuecomment-183654871
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 cl4es commented on the pull request:
https://github.com/apache/spark/pull/11160#issuecomment-183662509
This should likely be refactored to a place where both sbt and test code
can access it, but I hope this is good enough.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11160#issuecomment-183663172
**[Test build #51241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51241/consoleFull)**
for PR 11160 at commit
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-183672135
Yes: oozie gets all the tokens, but it has to hand them down. That env var
is how it does it. As it is the spark client always tries to retrieve those
tokens if
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11160#issuecomment-183685816
**[Test build #51241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51241/consoleFull)**
for PR 11160 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11160#issuecomment-183685861
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/11160#issuecomment-183685860
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 BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10411#discussion_r52829428
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaALSExample.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10411#discussion_r52829527
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaALSExample.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-183699703
oozie does it through the UGI and doAs and filling in the credentials.
Otherwise it wouldn't work for me now with Spark.
That is why I'm trying to understand
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10411#discussion_r52830051
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaALSExample.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10411#discussion_r52830580
--- Diff: docs/mllib-collaborative-filtering.md ---
@@ -32,16 +32,16 @@ following parameters:
The standard approach to matrix factorization
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10411#discussion_r52830587
--- Diff: docs/ml-collaborative-filtering.md ---
@@ -0,0 +1,147 @@
+---
+layout: global
+title: Collaborative Filtering - spark.ml
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10411#issuecomment-183707910
**[Test build #51242 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51242/consoleFull)**
for PR 10411 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10411#issuecomment-183717003
**[Test build #51242 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51242/consoleFull)**
for PR 10411 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10411#issuecomment-183717044
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/10411#issuecomment-183717042
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 flyjy commented on a diff in the pull request:
https://github.com/apache/spark/pull/8056#discussion_r52831393
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/ResolvedDataSource.scala
---
@@ -0,0 +1,204 @@
+/*
+* Licensed to the
GitHub user tanwanirahul opened a pull request:
https://github.com/apache/spark/pull/11194
[SPARK-13309][SQL] Fix type inference issue with CSV data
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tanwanirahul/spark master
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11194#issuecomment-183726195
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183728223
**[Test build #51243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51243/consoleFull)**
for PR 11148 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/11195
[SPARK-13236] SQL Generation for Set Operations
This PR is to implement SQL generation for the following three set
operations:
- Union Distinct
- Intersect
- Except
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183731255
I've updated this to fix compilation after that SQLBuilder change. One
quick question: do we have to worry about the logical plan -> SQL conversion
being applied to
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10705#discussion_r52832524
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockInfoManager.scala ---
@@ -0,0 +1,335 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11195#issuecomment-183736465
**[Test build #51244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51244/consoleFull)**
for PR 11195 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183737298
IMO, in the future, if we need to convert the optimized plans to SQL, we
need to add a few rules in SQLBuilder to revert back the changes of some
optimization
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183753884
**[Test build #51243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51243/consoleFull)**
for PR 11148 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11191#issuecomment-183624291
Please close 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 does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183624342
**[Test build #51229 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51229/consoleFull)**
for PR 11100 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11102#issuecomment-183632593
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/11102#issuecomment-183632594
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/11102#issuecomment-183632590
**[Test build #51239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51239/consoleFull)**
for PR 11102 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183624395
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/11100#issuecomment-183624394
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 hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/11102#issuecomment-183625102
@mengxr Thanks for the review. Sorry for the late response, I was on a
flight.
It's great to know DataFrame.stat.sampleB. One concern is that it does not
allow
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11160#discussion_r52825264
--- Diff: project/SparkBuild.scala ---
@@ -167,8 +167,8 @@ object SparkBuild extends PomBuild {
publishLocalBoth <<= Seq(publishLocal in
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183624567
@rxin After searching the code base, all the samples are table sample.
Could you give me more hints? I also agree it looks brittle. I did my best to
make it more
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11135
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11135#issuecomment-183625373
Merged to master/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 not have this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11182#issuecomment-183625416
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
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183625392
@davies Already deprecated `GROUPING__ID` in the latest commits and also
clean all the test cases.
Also tried to output a better error message when users
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183623495
**[Test build #51234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51234/consoleFull)**
for PR 11121 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183624744
**[Test build #51236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51236/consoleFull)**
for PR 11148 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183624724
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/10894#issuecomment-183624679
**[Test build #51232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51232/consoleFull)**
for PR 10894 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183624694
You can for example in the Sample operator add a method that returns true
if it is created from table sample in the parser.
---
If your project is set up for it, you
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183624711
Basically it'd be better to have something very explicit, rather than
relying on some conditions that might change in the future.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183624725
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11091#issuecomment-183625276
@YPares are you going to update this or should I continue it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11160#issuecomment-183625244
I think `UtilsSuite` still needs a treatment.
I think the code and scripts attempt to not set MaxPermSize for Java 8
already. If it doesn't somewhere, that also
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11182#issuecomment-183625936
**[Test build #51238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51238/consoleFull)**
for PR 11182 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183753976
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/11148#issuecomment-183753974
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/10527#issuecomment-183624210
**[Test build #51235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51235/consoleFull)**
for PR 10527 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11148#discussion_r52825188
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/SQLBuilder.scala ---
@@ -80,6 +81,26 @@ class SQLBuilder(logicalPlan: LogicalPlan,
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11148#issuecomment-183624788
@rxin I see. Will do it. 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-183625576
**[Test build #51237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51237/consoleFull)**
for PR 10539 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11102#issuecomment-183632084
**[Test build #51239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51239/consoleFull)**
for PR 11102 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10527#issuecomment-183632986
**[Test build #51235 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51235/consoleFull)**
for PR 10527 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11195#issuecomment-183755383
**[Test build #51244 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51244/consoleFull)**
for PR 11195 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11195#issuecomment-183755443
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/11195#issuecomment-183755445
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11196#issuecomment-183759705
Thanks for looking at this, but I'm not sure that this minor style cleanup
adds a whole lot of value so I'd prefer not to do this type of local cleanup
for cleanup's
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/11197
[SPARK-13302][PYSPARK][TESTS] Move the temp file creation and cleanup
outside of the doctests
Some of the new doctests in ml/clustering.py have a lot of setup code, move
the setup code to the
Github user financeCoding closed the pull request at:
https://github.com/apache/spark/pull/11196
---
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
Github user financeCoding commented on the pull request:
https://github.com/apache/spark/pull/11196#issuecomment-183763058
sgtm, was looking at low hanging fruit while I get acclimated with spark.
---
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/11197#issuecomment-183763478
**[Test build #51245 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51245/consoleFull)**
for PR 11197 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11193#discussion_r52834480
--- Diff:
network/common/src/main/java/org/apache/spark/network/protocol/MessageEncoder.java
---
@@ -49,11 +49,15 @@ public void
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183767434
**[Test build #51248 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51248/consoleFull)**
for PR 10705 at commit
GitHub user financeCoding opened a pull request:
https://github.com/apache/spark/pull/11196
[Style] Minor style change on CoarseGrainedExecutorBackend
* Removed unnecessary brackets
* Idiomatic usage of `argv.nonEmpty` instead of `!argv.isEmpty`
You can merge this pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11196#issuecomment-183759084
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11197#issuecomment-183764928
**[Test build #51245 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51245/consoleFull)**
for PR 11197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11197#issuecomment-183764956
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/11197#issuecomment-183764955
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/11193#issuecomment-183766617
**[Test build #51246 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51246/consoleFull)**
for PR 11193 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183766952
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
1 - 100 of 204 matches
Mail list logo
