Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-58448285
@marmbrus any more comments on 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-58450977
Thanks, I've merged this 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2559
---
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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/2559#discussion_r18622458
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -74,7 +81,7 @@ class AnalysisSuite extends FunSuite
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2559#discussion_r18561411
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -74,7 +81,7 @@ class AnalysisSuite extends
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-58296604
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-58296973
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21439/consoleFull)
for PR 2559 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-58300982
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/2559#issuecomment-58300979
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21439/consoleFull)
for PR 2559 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2559#discussion_r18263943
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -74,7 +81,7 @@ class AnalysisSuite extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57427168
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21096/consoleFull)
for PR 2559 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57427571
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/2559#issuecomment-57427564
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21096/consoleFull)
for PR 2559 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57522629
Looks like the failure is a legitimate compilation problem.
---
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/2559#issuecomment-57265657
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/2559#issuecomment-57265653
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21018/consoleFull)
for PR 2559 at commit
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/2559#discussion_r18199560
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -74,7 +81,7 @@ class AnalysisSuite extends
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57082094
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57082251
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20936/consoleFull)
for PR 2559 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57084958
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20936/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57084960
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/2559
[SPARK-3707] [SQL] Fix bug of type coercion in DIV
Calling `BinaryArithmetic.dataType` will throws exception until it's
resolved, but in type coercion rule `Division`, seems doesn't follow
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57055354
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20917/consoleFull)
for PR 2559 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57058942
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/2559#issuecomment-57058940
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20917/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57062261
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/170/consoleFull)
for PR 2559 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2559#issuecomment-57065586
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/170/consoleFull)**
after a configured wait of `120m`.
---
If your project
27 matches
Mail list logo
