Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9807#issuecomment-163688796
**[Test build #47511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47511/consoleFull)**
for PR 9807 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9807#issuecomment-163688975
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user dereksabryfb commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163699828
Added a case for sort
---
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/10191#issuecomment-163699843
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/10240#issuecomment-163704082
**[Test build #47528 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47528/consoleFull)**
for PR 10240 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10246#issuecomment-163706432
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/10220#issuecomment-163706535
@felixcheung Could you see if this satisfies the requirements in
https://issues.apache.org/jira/browse/SPARK-10346 ? The only other thing we had
in mind was to match
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/9925#issuecomment-163708919
I agree that its not pretty, however the only other fix I see is to remove
"$" for columns instead
---
If your project is set up for it, you can reply to this email
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10179#issuecomment-163712455
@anabranch Hm, I may not have been clear enough. The save/load
functionality seems general and important enough that it should go under the
"Main concepts in
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10234#discussion_r47264940
--- Diff: docs/ml-classification-regression.md ---
@@ -27,10 +27,10 @@ displayTitle: Classification and regression in spark.ml
* This will become a table
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163714372
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/10204#issuecomment-163714745
**[Test build #47527 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47527/consoleFull)**
for PR 10204 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10240#discussion_r47267569
--- Diff:
core/src/main/scala/org/apache/spark/memory/ExecutionMemoryPool.scala ---
@@ -91,23 +108,34 @@ private[memory] class ExecutionMemoryPool(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10236#issuecomment-163716622
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/10057#issuecomment-163689616
**[Test build #47497 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47497/consoleFull)**
for PR 10057 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9923#issuecomment-163690659
**[Test build #47525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47525/consoleFull)**
for PR 9923 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10204#issuecomment-163690621
**[Test build #47527 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47527/consoleFull)**
for PR 10204 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10191#issuecomment-163699540
**[Test build #47518 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47518/consoleFull)**
for PR 10191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-163701403
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163701442
ok, 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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163701557
Last commit actually passed tests last night.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10208#issuecomment-163705815
**[Test build #47529 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47529/consoleFull)**
for PR 10208 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10250#issuecomment-163708398
I have merged it. Let's 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10209#issuecomment-163710755
**[Test build #47531 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47531/consoleFull)**
for PR 10209 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10209#discussion_r47267922
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -122,11 +122,22 @@ case class Except(left:
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10218#issuecomment-163718935
I'm not sure this is worth the complexity. I think most users will only
ever drop by name (since dropping a complex expression doesn't really make
sense), and in
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163719076
In addition to moving ml-intro back to ml-guide, it'd be nice if the
sidebar had links back to the main spark.ml and spark.mllib pages. That could
be done in a
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10209#discussion_r47268378
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -99,6 +99,13 @@ abstract class LogicalPlan
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163722755
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/10228#issuecomment-163726187
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163728332
I'd try the following locally `build/sbt scalastyle test:scalastyle
catalyst/test sql/test`.
Each of those commands can be run separately too and you can use
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163729292
**[Test build #47538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47538/consoleFull)**
for PR 10052 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10240#discussion_r47275498
--- Diff:
core/src/main/scala/org/apache/spark/memory/ExecutionMemoryPool.scala ---
@@ -91,23 +108,34 @@ private[memory] class ExecutionMemoryPool(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163731886
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/10228#discussion_r47276008
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/AggregationIterator.scala
---
@@ -165,155 +134,52 @@ abstract class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163734167
**[Test build #47538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47538/consoleFull)**
for PR 10052 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163734214
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/10208#issuecomment-163733865
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/10208#issuecomment-163733716
**[Test build #47529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47529/consoleFull)**
for PR 10208 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163737620
That's the only remaining issue I found. I checked against the Spark 1.5
doc links as well.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9923#issuecomment-163716405
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163718318
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10243#issuecomment-163720242
+1 to @rxin concerns on wrapping. A good rule of thumb is to always break
at the highest syntatic level (not in the middle of some construct like a list
of
Github user drcrallen commented on the pull request:
https://github.com/apache/spark/pull/10232#issuecomment-163724877
Doesn't affect heap memory properly, closing until fixed
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163726273
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/10228#issuecomment-163726125
**[Test build #47533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47533/consoleFull)**
for PR 10228 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/10254#discussion_r47274373
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -155,6 +155,11 @@ case class
Github user jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/10231#discussion_r47274795
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/RandomForest.scala ---
@@ -842,60 +842,63 @@ private[ml] object RandomForest extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163731702
**[Test build #47537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47537/consoleFull)**
for PR 10234 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163731884
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/10240#issuecomment-163731260
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 nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/10228#discussion_r47276459
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/AggregationIterator.scala
---
@@ -49,41 +47,20 @@ abstract class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163734217
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/10236
---
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/10234#discussion_r47278589
--- Diff: docs/ml-survival-regression.md ---
@@ -1,7 +1,7 @@
---
layout: global
-title: Survival Regression - ML
-displayTitle: ML -
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10240#discussion_r47268739
--- Diff:
core/src/main/scala/org/apache/spark/memory/ExecutionMemoryPool.scala ---
@@ -91,23 +108,34 @@ private[memory] class ExecutionMemoryPool(
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10209#discussion_r47268048
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/plans/PlanTest.scala
---
@@ -43,7 +43,7 @@ abstract class PlanTest extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10228#issuecomment-163720246
**[Test build #47533 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47533/consoleFull)**
for PR 10228 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9138#issuecomment-163719606
@vanzin just found an issue about this change. Now if the master receives
`RegisterWorker`, it won't use the `workerRef` to send the reply. So there is
no connection
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10174#discussion_r47270183
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/DefaultOptimizerExtendableSuite.scala
---
@@ -0,0 +1,45 @@
+/*
+ * Licensed to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163722742
**[Test build #47534 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47534/consoleFull)**
for PR 10052 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163722112
**[Test build #47534 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47534/consoleFull)**
for PR 10052 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163722357
**[Test build #47535 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47535/consoleFull)**
for PR 10234 at commit
Github user thunterdb commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163723975
@jkbradley done:
https://cloud.githubusercontent.com/assets/7594753/11725710/e9949f04-9f2f-11e5-8ba5-7f955e8b41fa.png;>
---
If your project is set up for it,
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/10186#discussion_r47273371
--- Diff: python/pyspark/ml/feature.py ---
@@ -2093,6 +2093,95 @@ class RFormulaModel(JavaModel):
"""
+@inherit_doc
+class
Github user dereksabryfb commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163727440
Apologies, I haven't been able to run ./dev/run-tests, getting the
following exception: http://pastebin.com/L0p0sjtJ
so I wasn't able to pick up the style
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10234#issuecomment-163727576
**[Test build #47537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47537/consoleFull)**
for PR 10234 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163731070
**[Test build #47528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47528/consoleFull)**
for PR 10240 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163731262
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/10209#issuecomment-163732061
**[Test build #47531 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47531/consoleFull)**
for PR 10209 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10209#issuecomment-163732157
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/10208#issuecomment-163733868
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10204#issuecomment-163734579
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10204#issuecomment-163734657
Thanks! 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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10236#issuecomment-163734799
The only change is to remove that `require`. I am merging it to master and
branch 1.6.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10236#issuecomment-163716624
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10254#discussion_r47269588
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -155,6 +155,11 @@ case class InsertIntoHiveTable(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10052#issuecomment-163722753
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/10228#issuecomment-163724932
**[Test build #47536 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47536/consoleFull)**
for PR 10228 at commit
Github user drcrallen closed the pull request at:
https://github.com/apache/spark/pull/10232
---
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/10234#issuecomment-163726109
**[Test build #47535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47535/consoleFull)**
for PR 10234 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10228#issuecomment-163726189
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/10234#issuecomment-163726277
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/10154#discussion_r47274898
--- Diff: core/src/main/scala/org/apache/spark/ui/exec/ExecutorsPage.scala
---
@@ -33,11 +33,13 @@ private[ui] case class ExecutorSummaryInfo(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10209#issuecomment-163732156
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 felixcheung commented on the pull request:
https://github.com/apache/spark/pull/10220#issuecomment-163732757
Sure, I'll check. We were discussing a bit in SPARK-12235
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10204
---
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/10238#issuecomment-163737331
**[Test build #47532 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47532/consoleFull)**
for PR 10238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10238#issuecomment-163737414
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/10238#issuecomment-163737413
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163738746
@davies please look at the final changes.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10240#issuecomment-163738626
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10249#issuecomment-163684431
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/10255#issuecomment-163684045
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/9908#issuecomment-163690187
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/9158#issuecomment-163692088
[Test build #47506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47506/console)
for PR 9158 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10236#issuecomment-163691816
**[Test build #47526 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47526/consoleFull)**
for PR 10236 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9158#issuecomment-163692307
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 does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9158#issuecomment-163692308
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/9957#issuecomment-163693631
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 616 matches
Mail list logo
