Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14615
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76766/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #76766 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76766/testReport)**
for PR 14615 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #76766 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76766/testReport)**
for PR 14615 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14615
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76757/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #76757 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76757/testReport)**
for PR 14615 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #76757 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76757/testReport)**
for PR 14615 at commit
Github user robert3005 commented on the issue:
https://github.com/apache/spark/pull/14615
thanks @gatorsmile, updated
---
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 robert3005 commented on the issue:
https://github.com/apache/spark/pull/14615
ping? @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 feature
enabled and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74828/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
**[Test build #74828 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74828/testReport)**
for PR 14615 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74828 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74828/testReport)**
for PR 14615 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74759/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74759 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74759/testReport)**
for PR 14615 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74759 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74759/testReport)**
for PR 14615 at commit
Github user robert3005 commented on the issue:
https://github.com/apache/spark/pull/14615
It indeed does look like a flake.
---
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 ash211 commented on the issue:
https://github.com/apache/spark/pull/14615
Jenkins, this is 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
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14615
@robert3005 looks like this has unit test failures on
`org.apache.spark.sql.hive.orc.OrcSourceSuite.SPARK-19459/SPARK-18220: read
char/varchar column written by Hive` -- is that a flake?
---
If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74755/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74755 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74755/testReport)**
for PR 14615 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74755 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74755/testReport)**
for PR 14615 at commit
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14615
Jenkins, this is 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
Github user robert3005 commented on the issue:
https://github.com/apache/spark/pull/14615
@rxin any chance you or someone else can take a look?
---
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 ash211 commented on the issue:
https://github.com/apache/spark/pull/14615
This seems pretty reasonable, assuming test coverage already exists on that
toJSON method.
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email
Github user robert3005 commented on the issue:
https://github.com/apache/spark/pull/14615
@rxin anything else? I added docs to the best of my understanding let me
know if you meant something else.
---
If your project is set up for it, you can reply to this email and have your
reply
31 matches
Mail list logo