Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61395835
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/3059#issuecomment-61395832
[Test build #22743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22743/consoleFull)
for PR 3059 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3059
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/3059
[SPARK-4182][SQL] Fixes ColumnStats classes for boolean, binary and complex
data types
`NoopColumnStats` was once used for binary, boolean and complex data types.
This `ColumnStats` doesn't
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61393214
[Test build #22734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22734/consoleFull)
for PR 3059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61393299
[Test build #22736 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22736/consoleFull)
for PR 3059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61393901
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/3059#issuecomment-61393900
[Test build #22734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22734/consoleFull)
for PR 3059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61393956
[Test build #22736 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22736/consoleFull)
for PR 3059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61393958
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61394703
Hm, the above test failure is legitimate. However, the test failure is
sensitive to execution order, namely, it only fails when some test case had
cached the test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3059#issuecomment-61394788
[Test build #22743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22743/consoleFull)
for PR 3059 at commit
12 matches
Mail list logo
