Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15512
LGTM. Merging to master. Thanks!
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15512
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67102/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15512
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/15512
**[Test build #67102 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67102/consoleFull)**
for PR 15512 at commit
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/15512
I also think that the time saved is all the registration which can be
skipped, but did not verify.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15512
**[Test build #67102 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67102/consoleFull)**
for PR 15512 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15512
**[Test build #67065 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67065/consoleFull)**
for PR 15512 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15512
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/15512
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67065/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15512
**[Test build #67065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67065/consoleFull)**
for PR 15512 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/15512
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
Github user squito commented on the issue:
https://github.com/apache/spark/pull/15512
serializing will create buffers, but since these are only used for
deserializing, I don't think there should even be any buffers created. I guess
the time saved is all the registration which can be
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15512
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/15512
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67063/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15512
**[Test build #67063 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67063/consoleFull)**
for PR 15512 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15512
Hm, if the benchmark you give generalizes much that is certainly
compelling. I guess I'm surprised that instantiating the object can be so
expensive relative to deserialization since it just happens
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15512
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 wishes so, or if
17 matches
Mail list logo
