Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16862
We can remove the `putBytes` workaround when I (or someone else) get around
to fixing SPARK-19556.
For now, I'm merging this to master and 2.1.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16862
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72667/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16862
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/16862
**[Test build #72667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72667/testReport)**
for PR 16862 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16862
**[Test build #72667 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72667/testReport)**
for PR 16862 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16862
Looks good.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16862
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72654/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16862
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/16862
**[Test build #72654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72654/testReport)**
for PR 16862 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16862
**[Test build #72654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72654/testReport)**
for PR 16862 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16862
Kafka test error (hopefully unrelated?). 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
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16862
@liancheng FYI
---
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/16862
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72614/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16862
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/16862
**[Test build #72614 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72614/testReport)**
for PR 16862 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16862
**[Test build #72614 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72614/testReport)**
for PR 16862 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16862
@tdas @zsxwing
---
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
17 matches
Mail list logo