Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18553
Thanks for reviewing! 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
ena
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79304/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79304 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79304/testReport)**
for PR 18553 at commit
[`15b7497`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79304 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79304/testReport)**
for PR 18553 at commit
[`15b7497`](https://github.com/apache/spark/commit/15
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18553
Jenkins, 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 this feature
enabled and wis
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79291/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79291/testReport)**
for PR 18553 at commit
[`15b7497`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79291/testReport)**
for PR 18553 at commit
[`15b7497`](https://github.com/apache/spark/commit/15
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18553
This was a good catch I believe. I manually checked each byte between
Python 2 and Python 3 pickled one.
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18553
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79274/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79274 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79274/testReport)**
for PR 18553 at commit
[`c729eff`](https://github.com/apache/spark/commit/c
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18553
cc @holdenk, @HyukjinKwon, @zasdfgbnm
---
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
enable
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18553
**[Test build #79274 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79274/testReport)**
for PR 18553 at commit
[`c729eff`](https://github.com/apache/spark/commit/c7
16 matches
Mail list logo
