Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16155
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16142
cc @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 feature
enabled and wishes so, or if
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/16164
[SPARK-18732][WEB-UI] The Y axis ranges of "schedulingDelay",
"processingTime"â¦
## What changes were proposed in this pull request?
Currently, the Y axis ranges of "schedulingDelay",
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91002601
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -132,50 +153,80 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91002427
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -132,50 +153,80 @@ case class
Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16006#discussion_r91001763
--- Diff:
external/kafka-0-10/src/main/scala/org/apache/spark/streaming/kafka010/DirectKafkaInputDStream.scala
---
@@ -67,6 +67,10 @@ private[spark]
Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16006#discussion_r91002372
--- Diff:
external/kafka-0-10/src/main/scala/org/apache/spark/streaming/kafka010/DirectKafkaInputDStream.scala
---
@@ -143,9 +147,14 @@ private[spark]
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15994
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91002161
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/ExpressionEvalHelper.scala
---
@@ -59,12 +59,36 @@ trait
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15994
@windpiger you should use a proper email on your github commit next time.
It is currently shown as:
```
Enter primary author in the format of "name " [root
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15994
Thanks - merging in 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 this feature
enabled and
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16147
Thank you so much @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 feature
enabled
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16157#discussion_r91002001
--- Diff: docs/programming-guide.md ---
@@ -347,7 +347,7 @@ Some notes on reading files with Spark:
Apart from text files, Spark's Scala API also
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91001752
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -56,28 +56,49 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91001488
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -56,28 +56,49 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91001362
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/encoders/ExpressionEncoder.scala
---
@@ -50,7 +50,7 @@ object ExpressionEncoder {
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16155
Merging to master and 2.1
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16155
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69700/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16155
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 project does not have this feature
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15998#discussion_r91001189
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/catalog/ExternalCatalogSuite.scala
---
@@ -346,6 +346,31 @@ abstract class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16155
**[Test build #69700 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69700/consoleFull)**
for PR 16155 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r91000921
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16152
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/16131#discussion_r91000876
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -505,7 +505,8 @@ object GeneralizedLinearRegression
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16152
LGTM, 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 this feature
enabled and
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16161#discussion_r91000691
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/encoders/RowEncoder.scala
---
@@ -288,7 +287,7 @@ object RowEncoder {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r91000387
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +488,45 @@ class HiveUDFSuite extends QueryTest
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16113
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r91000126
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class Generate(
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16163
It might not be exactly the same thing, but I remember we changed something
like this in the opposite way -- to link straight to the full output since
typically you need that to debug a failure, and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16162
---
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 issue:
https://github.com/apache/spark/pull/16113
Merging to master and 2.1
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69699/
Test PASSed.
---
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r9021
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class Generate(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16162
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 project does not have this feature
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16162
Merging to master and 2.1
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16162
**[Test build #69699 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69699/consoleFull)**
for PR 16162 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16159#discussion_r90999547
--- Diff: project/SparkBuild.scala ---
@@ -596,19 +596,17 @@ object Hive {
}
object Assembly {
- import sbtassembly.AssemblyUtils._
-
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r90999177
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15998
Yea this one seems like directly related to the work we did in 2.1 for
large table handling.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16147
Hi @srowen I just manually downloaded spark 2.1.0 rc1 and then tested as
below:
I tested both
```
.\bin\spark-shell.cmd --master local-cluster[2,1,1024]
```
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15998
LGTM, @rxin shall we backport this? Although it's not a bug, it's a
scalability issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16120
Thank you! @hvanhovell
---
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16128#discussion_r90997809
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/FileStreamSourceSuite.scala
---
@@ -1022,6 +1021,33 @@ class FileStreamSourceSuite extends
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16128#discussion_r90997211
--- Diff:
external/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/JsonUtils.scala
---
@@ -81,7 +81,14 @@ private object JsonUtils {
*/
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16128#discussion_r9099
--- Diff:
external/kafka-0-10-sql/src/test/scala/org/apache/spark/sql/kafka010/KafkaSourceOffsetSuite.scala
---
@@ -89,4 +89,16 @@ class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16120
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16120
LGTM - merging to master/2.1/2.0 (if possible). Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r90997370
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16092
@foxish this need to be rebased.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16113
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16113
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69695/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16113
**[Test build #69695 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69695/consoleFull)**
for PR 16113 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16162
Thanks @zsxwing LGTM2!
---
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
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16000#discussion_r90996869
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/StreamingListener.scala
---
@@ -66,6 +69,9 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16160
**[Test build #69706 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69706/consoleFull)**
for PR 16160 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16120#discussion_r90996775
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -93,13 +93,13 @@ case class Generate(
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16162
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 and wishes so, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16146
**[Test build #69707 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69707/consoleFull)**
for PR 16146 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16160
Forgot that `lastProgress` may be the batch without data. Updated the test
to drop no data progress.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16160
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16160
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69697/
Test PASSed.
---
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16146
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
enabled and wishes so, or if
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16160
**[Test build #69697 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69697/consoleFull)**
for PR 16160 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15780
oh sorry I thought incorrect nullability is also a bug... yea this change
is too large to backport, I'll be more careful in the future.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
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 not have this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16053
**[Test build #69702 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69702/consoleFull)**
for PR 16053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69702/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16160
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69698/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16160
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16128
**[Test build #69705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69705/consoleFull)**
for PR 16128 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16159
**[Test build #69704 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69704/consoleFull)**
for PR 16159 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16160
**[Test build #69698 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69698/consoleFull)**
for PR 16160 at commit
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/16159
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 feature
enabled and wishes
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/16159
It failed the unit test:
`org.apache.spark.sql.streaming.StreamingQueryListenerSuite.single listener,
check trigger events are generated correctly`. However, I just ran it locally,
and it passed.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16163
**[Test build #69703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69703/testReport)**
for PR 16163 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/16163
[SPARK-18730] Post Jenkins test report page instead of the full console
output page to GitHub
## What changes were proposed in this pull request?
Currently, the full console output page
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16053
**[Test build #69702 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69702/consoleFull)**
for PR 16053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16155
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16155
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69694/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16155
**[Test build #69694 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69694/consoleFull)**
for PR 16155 at commit
Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/15992
---
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 issue:
https://github.com/apache/spark/pull/15998
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69691/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15998
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15998
**[Test build #69691 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69691/consoleFull)**
for PR 15998 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16160
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 and wishes so, or if the
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16160#discussion_r90992578
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/streaming/ForeachSinkSuite.scala
---
@@ -204,6 +204,55 @@ class ForeachSinkSuite extends
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16154
@shivaram PR seems ready for you to make a pass:)
---
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 issue:
https://github.com/apache/spark/pull/16053
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69701/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16053
**[Test build #69701 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69701/consoleFull)**
for PR 16053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
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 not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16159
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16159
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69692/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16053
**[Test build #69701 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69701/consoleFull)**
for PR 16053 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16159
**[Test build #69692 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69692/consoleFull)**
for PR 16159 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16160#discussion_r90990663
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/streaming/ForeachSinkSuite.scala
---
@@ -204,6 +204,55 @@ class ForeachSinkSuite extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16161
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69696/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16161
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16161
**[Test build #69696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69696/consoleFull)**
for PR 16161 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16155
Still LGTM. Merge when tests pass on the latest commit.
---
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
101 - 200 of 511 matches
Mail list logo
