Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9770#issuecomment-157489311
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/9749#issuecomment-157494844
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/9774#issuecomment-157496670
**[Test build #46105 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46105/consoleFull)**
for PR 9774 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-157496541
It's looking good. If there are no further comments I'll merge shortly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45116927
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+ *
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-157500280
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157501389
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157502460
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 a diff in the pull request:
https://github.com/apache/spark/pull/9770#discussion_r45104293
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -1063,6 +1065,29 @@ class Analyzer(
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9649#issuecomment-157474961
Thanks, I'm going to merge this to 1.6 and 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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9649#discussion_r45105488
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/StructType.scala ---
@@ -328,7 +328,8 @@ object StructType extends AbstractDataType {
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9749#discussion_r45106138
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/util/DefaultReadWriteTest.scala ---
@@ -64,6 +66,47 @@ trait DefaultReadWriteTest extends TempDirectory {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9761#issuecomment-157476327
**[Test build #46095 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46095/consoleFull)**
for PR 9761 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9662#issuecomment-157478570
Thanks, I'm going to merge this into master and 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9705#issuecomment-157480825
This looks good to me, but I think the title needs to be updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157496127
**[Test build #46106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46106/consoleFull)**
for PR 9773 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157501177
**[Test build #46097 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46097/consoleFull)**
for PR 9742 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157501387
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 schot commented on the pull request:
https://github.com/apache/spark/pull/9767#issuecomment-157503489
If I understand the discussion in SPARK-3266 correctly the method should
only be added to the JavaRRDLike trait and not the abstract class.
I have updated the PR
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157508378
**[Test build #46110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46110/consoleFull)**
for PR 9749 at commit
GitHub user sethah opened a pull request:
https://github.com/apache/spark/pull/9777
[SPARK-11108][ML] OneHotEncoder should support other numeric types
Adding support for other numeric types:
* Integer
* Short
* Long
* Float
* Decimal
You can merge this pull
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9764#issuecomment-157515018
I don't think `array_contains` or `sort_array ` should mask anything in
base or stats.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9777#issuecomment-157517769
**[Test build #46112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46112/consoleFull)**
for PR 9777 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9707#issuecomment-157517442
**[Test build #46113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46113/consoleFull)**
for PR 9707 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157518450
We overrided `jsonEncode`/`jsonDecode` for basic param types. This could be
simpler if we added class tags or associate schema with the parameters.
---
If your project
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/9778
[SPARK-11790][Streaming][Tests]Increase the connection timeout
Sometimes, EmbeddedZookeeper may need more than 6 seconds to setup up in a
slow Jenkins worker. So just increase the timeout, it won't
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157520609
**[Test build #46103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46103/consoleFull)**
for PR 9772 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9716#discussion_r45127348
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/RandomForestClassifierExample.scala
---
@@ -0,0 +1,99 @@
+/*
+ * Licensed to the
GitHub user choochootrain opened a pull request:
https://github.com/apache/spark/pull/9779
[SPARK-11195][CORE] Use correct classloader for TaskResultGetter
Make sure we are using the context classloader when deserializing failed
TaskResults instead of the Spark classloader.
Github user choochootrain commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157522927
@yhuai any other comments?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9713
---
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 thunterdb commented on the pull request:
https://github.com/apache/spark/pull/9697#issuecomment-157523631
Thank you @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 project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157527154
**[Test build #46116 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46116/consoleFull)**
for PR 9780 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9772
---
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/9778#issuecomment-157529795
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/9481#issuecomment-157531954
**[Test build #46117 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46117/consoleFull)**
for PR 9481 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157507608
Unrelated failure.
This LGTM.
My only comment is that the implementation assumes we won't add many Param
types support by the default jsonEncode.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157507913
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9654#issuecomment-157513119
any more comment?
---
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/9707#discussion_r45124403
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/Checkpoint.scala ---
@@ -187,16 +187,27 @@ class CheckpointWriter(
private var stopped =
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9750#issuecomment-157512986
this PR is documentation only, no code change here
---
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 the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157516407
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157521027
**[Test build #2082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2082/consoleFull)**
for PR 9776 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157520798
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/9772#issuecomment-157520799
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9716#issuecomment-157522120
LGTM except one issue commented inline. Please keep the example code the
same while moving them around. It is easier for review.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157521919
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6665#discussion_r45132241
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/StandardScalerSuite.scala ---
@@ -0,0 +1,108 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6665#issuecomment-157530682
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/6665#issuecomment-157530732
LGTM pending Jenkins.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157507905
**[Test build #46109 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46109/consoleFull)**
for PR 9656 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157507912
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 tedyu commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157508125
@tdas @zsxwing
Any feedback ?
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9736#discussion_r45122717
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/linalg/distributed/RowMatrix.scala
---
@@ -379,25 +379,43 @@ class RowMatrix @Since("1.0.0") (
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9680#issuecomment-157513054
any more comment?
---
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 the pull request:
https://github.com/apache/spark/pull/9707#issuecomment-157514153
Added a unit test using mock
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/9758#discussion_r45127540
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -258,7 +258,8 @@ private[spark] class Client(
if (executorMem >
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157523161
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157523670
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9749
---
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 opened a pull request:
https://github.com/apache/spark/pull/9780
[SPARK-11789] [core] [yarn] Lower severity of some executor loss logs.
Don't log ERROR messaged when executors are explicitly killed or when
the exit reason is not yet known.
You can merge this
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157529318
Merging master/1.6/1.5.
---
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/9777#issuecomment-157531093
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/9777#issuecomment-157512040
**[Test build #46111 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46111/consoleFull)**
for PR 9777 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157514509
/cc @zsxwing
---
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 felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/9764#discussion_r45124871
--- Diff: R/pkg/R/functions.R ---
@@ -2365,3 +2333,74 @@ setMethod("rowNumber",
jc <- callJStatic("org.apache.spark.sql.functions",
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/9764#discussion_r45124823
--- Diff: R/pkg/R/functions.R ---
@@ -2365,3 +2333,74 @@ setMethod("rowNumber",
jc <- callJStatic("org.apache.spark.sql.functions",
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9722#issuecomment-157518974
cc: @feynmanliang
---
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/9749#issuecomment-157521754
**[Test build #46110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46110/consoleFull)**
for PR 9749 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9778#issuecomment-157521848
**[Test build #46114 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46114/consoleFull)**
for PR 9778 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157521921
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9713#issuecomment-157522756
LGTM. 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9776
---
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/9742#issuecomment-157525321
**[Test build #46115 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46115/consoleFull)**
for PR 9742 at commit
GitHub user RohanBhanderi opened a pull request:
https://github.com/apache/spark/pull/9781
Update usage directions in comment section according to correct classâ¦
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9781#issuecomment-157527576
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9705#discussion_r45131538
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Kurtosis.scala
---
@@ -37,13 +37,16 @@ case class Kurtosis(child:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9778#issuecomment-157529630
**[Test build #46114 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46114/consoleFull)**
for PR 9778 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9778#issuecomment-157529797
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/9777#issuecomment-157531089
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/9777#issuecomment-157530921
**[Test build #46112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46112/consoleFull)**
for PR 9777 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157532701
**[Test build #46119 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46119/consoleFull)**
for PR 9481 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-157612973
**[Test build #46177 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46177/consoleFull)**
for PR 8760 at commit
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
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
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
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):
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
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):
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
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
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
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
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 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
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):
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
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
801 - 900 of 939 matches
Mail list logo
