Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14952
I'm going to merge this into master and branch-2.0 as an immediate fix for
the PySpark caching issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14952
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 the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64925/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
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/14952
**[Test build #64925 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64925/consoleFull)**
for PR 14952 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14952
**[Test build #64925 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64925/consoleFull)**
for PR 14952 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64908/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
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/14952
**[Test build #64908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64908/consoleFull)**
for PR 14952 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14952
**[Test build #64908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64908/consoleFull)**
for PR 14952 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14952
/cc @ericl
---
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
11 matches
Mail list logo
