[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-25 Thread gatorsmile
Github user gatorsmile commented on the issue: https://github.com/apache/spark/pull/17408 Thanks! 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] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-25 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17408 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] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-25 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17408 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75215/ Test PASSed. ---

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-25 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17408 **[Test build #75215 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75215/testReport)** for PR 17408 at commit

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-25 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17408 **[Test build #75215 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75215/testReport)** for PR 17408 at commit

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread gatorsmile
Github user gatorsmile commented on the issue: https://github.com/apache/spark/pull/17408 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 feature enabled and wishes

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17408 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] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17408 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75156/ Test FAILed. ---

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17408 **[Test build #75156 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75156/testReport)** for PR 17408 at commit

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17408 **[Test build #75156 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75156/testReport)** for PR 17408 at commit

[GitHub] spark issue #17408: [SPARK-19949][SQL][follow-up] move FailureSafeParser fro...

2017-03-24 Thread cloud-fan
Github user cloud-fan commented on the issue: https://github.com/apache/spark/pull/17408 cc @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 this feature enabled and wishes so, or