Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13163#discussion_r63972318
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -59,6 +59,18 @@ public void testClusterCmdBuilder()
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13163#discussion_r63972414
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -59,6 +59,18 @@ public void testClusterCmdBuilder()
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220482444
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/13200#issuecomment-220482350
**[Test build #58911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58911/consoleFull)**
for PR 13200 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220482447
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rdblue commented on a diff in the pull request:
https://github.com/apache/spark/pull/12313#discussion_r63971653
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -348,28 +348,41 @@ case class
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63971344
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q31.sql
---
@@ -0,0 +1,60 @@
+WITH ss AS
+(SELECT
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13206#issuecomment-220480908
**[Test build #58915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58915/consoleFull)**
for PR 13206 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-220480521
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/13204#issuecomment-220480514
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/13204#issuecomment-220480353
**[Test build #58910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58910/consoleFull)**
for PR 13204 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63970987
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q78.sql
---
@@ -0,0 +1,64 @@
+WITH ws AS
+(SELECT
GitHub user rdblue opened a pull request:
https://github.com/apache/spark/pull/13206
[SPARK-15420] [SQL] Add repartition and sort to prepare output data
## What changes were proposed in this pull request?
* WriterContainer detects that the incoming logical plan has been
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220480244
cc @andrewor14 too who wrote some of this
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13163#issuecomment-220480180
**[Test build #58914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58914/consoleFull)**
for PR 13163 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220480176
**[Test build #58913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58913/consoleFull)**
for PR 13200 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13200#discussion_r63970867
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SparkSession.scala
---
@@ -738,26 +734,127 @@ object SparkSession {
* Gets an existing
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13200#discussion_r63970853
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SparkSession.scala
---
@@ -738,26 +734,127 @@ object SparkSession {
* Gets an existing
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13163#discussion_r63970749
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -59,6 +59,17 @@ public void
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/12837
---
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 jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/12152#discussion_r63970293
--- Diff: core/src/main/java/org/apache/spark/VersionInfo.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63970138
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q16.sql
---
@@ -0,0 +1,21 @@
+SELECT count(DISTINCT
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63970061
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q14a.sql
---
@@ -0,0 +1,121 @@
+WITH cross_items AS
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63969828
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q77.sql
---
@@ -0,0 +1,100 @@
+WITH ss AS
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220478320
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/13188#issuecomment-220478319
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/13188#issuecomment-220478265
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/13188#issuecomment-220478261
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/13188#issuecomment-220478172
**[Test build #58909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58909/consoleFull)**
for PR 13188 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220478082
**[Test build #58908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58908/consoleFull)**
for PR 13188 at commit
Github user jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/12152#discussion_r63969585
--- Diff: core/src/main/java/org/apache/spark/VersionInfo.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/12152#discussion_r63969372
--- Diff: core/src/main/java/org/apache/spark/VersionInfo.java ---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13196#issuecomment-220477551
**[Test build #2994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2994/consoleFull)**
for PR 13196 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13163#discussion_r63969163
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -59,6 +59,17 @@ public void testClusterCmdBuilder()
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63968968
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/q95.sql
---
@@ -0,0 +1,28 @@
+WITH ws_wh AS
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63968907
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/queries/ss_max.sql
---
@@ -0,0 +1,14 @@
+SELECT
--- End
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63968750
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/tpcds/TPCDSQueryBenchmark.scala
---
@@ -0,0 +1,132 @@
+/*
+ *
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/13205#issuecomment-220476667
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 the pull request:
https://github.com/apache/spark/pull/13201#issuecomment-220476068
cc @marmbrus @yhuai
---
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 Parth-Brahmbhatt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13150#discussion_r63968077
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/MetastoreRelation.scala ---
@@ -114,17 +115,27 @@ private[hive] case class
Github user Parth-Brahmbhatt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13150#discussion_r63968095
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/MetastoreRelation.scala ---
@@ -114,17 +115,27 @@ private[hive] case class
Github user Parth-Brahmbhatt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13150#discussion_r63968104
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/MetastoreRelation.scala ---
@@ -114,17 +115,27 @@ private[hive] case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13163#issuecomment-220475085
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/13163#issuecomment-220475084
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/13163#issuecomment-220474934
**[Test build #58903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58903/consoleFull)**
for PR 13163 at commit
Github user pwoody commented on the pull request:
https://github.com/apache/spark/pull/13178#issuecomment-220473754
Hey apologies for the late reply!
There are effectively two failure modes w.r.t the memory manager:
1. If you retain the SparkPlan then the broadcast
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/13198#issuecomment-220473337
Since this is a private API, this will not affect anything. Given that we
are using 'asML' now, I believe that it worths to make them consistent.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13205#issuecomment-220472283
**[Test build #58912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58912/consoleFull)**
for PR 13205 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13205#issuecomment-220471764
@yhuai
---
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 opened a pull request:
https://github.com/apache/spark/pull/13205
[SPARK-15421][SQL] Validate DDL property values
## What changes were proposed in this pull request?
When we parse DDLs involving table or database properties, we need to
validate the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220470605
**[Test build #58911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58911/consoleFull)**
for PR 13200 at commit
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/13196#issuecomment-220470402
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13201#issuecomment-220468953
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/13201#issuecomment-220468954
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/13201#issuecomment-220468768
**[Test build #58902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58902/consoleFull)**
for PR 13201 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220467898
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/13200#issuecomment-220467867
**[Test build #58907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58907/consoleFull)**
for PR 13200 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220467897
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/13204#issuecomment-220466925
**[Test build #58910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58910/consoleFull)**
for PR 13204 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-220466852
Another proposal is to have a special prefix for the operators that are
part of whole stage codegen.
```
>>> df = sqlCtx.range(1000);df2 =
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/13198#issuecomment-220466525
I agree "as" is more correct, but is this worth doing?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-220465870
cc @marmbrus @rxin
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220465759
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/13203#issuecomment-220465763
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/13203#issuecomment-220465663
**[Test build #58906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58906/consoleFull)**
for PR 13203 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/13204
explain of whole stage codegen
## What changes were proposed in this pull request?
Currently, the explain of a query with whole-stage codegen looks like this
```
>>> df =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13196#issuecomment-220464958
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/13196#issuecomment-220464957
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/13196#issuecomment-220464846
**[Test build #58879 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58879/consoleFull)**
for PR 13196 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220464858
**[Test build #58909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58909/consoleFull)**
for PR 13188 at commit
Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220464114
cc @davies
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220463818
**[Test build #58907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58907/consoleFull)**
for PR 13200 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220463800
**[Test build #58908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58908/consoleFull)**
for PR 13188 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220463575
@andrewor14 So the problem is that getOrCreate() is not aware of the
configuration (which could be different from the existing one), should we show
an warning on that?
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13160#issuecomment-220463295
I've done it here: https://github.com/apache/spark/pull/13200
---
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/13156#issuecomment-220461395
**[Test build #58905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58905/consoleFull)**
for PR 13156 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-220461429
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/13156#issuecomment-220461425
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-220461336
Great to see 900 lines were removed:)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/13101#discussion_r63959779
--- Diff: mllib/src/test/java/org/apache/spark/SharedSparkSession.java ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/13101#discussion_r63959615
--- Diff: mllib/src/test/java/org/apache/spark/SharedSparkSession.java ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220460463
**[Test build #58906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58906/consoleFull)**
for PR 13203 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220460020
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/13101#issuecomment-220459294
@techaddict thanks. One more comment. The rest looks pretty good.
---
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/13156#issuecomment-220459388
**[Test build #58905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58905/consoleFull)**
for PR 13156 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13101#discussion_r63958762
--- Diff: mllib/src/test/java/org/apache/spark/SharedSparkSession.java ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-220458174
I see. `spark.sessionState.invalidateTable` already exists. They have the
same implementation. Thus, I will just remove
`spark.sessionState.refreshTable`? Let me
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220457876
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/13203#issuecomment-220457875
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/13202#issuecomment-220457851
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/13203#issuecomment-220457842
**[Test build #58904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58904/consoleFull)**
for PR 13203 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13202#issuecomment-220457855
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/13202#issuecomment-220457620
**[Test build #58900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58900/consoleFull)**
for PR 13202 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13045#issuecomment-220456781
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/13045#issuecomment-220456786
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/13188#issuecomment-220456693
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/13188#issuecomment-220456688
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/13045#issuecomment-220456509
**[Test build #58896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58896/consoleFull)**
for PR 13045 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220456361
**[Test build #58892 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58892/consoleFull)**
for PR 13188 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220456009
@davies @gatorsmile
---
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
301 - 400 of 811 matches
Mail list logo
