Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16214
After rethinking this issue, I found this is not very appropriate as an
example delivered with Spark, since it depends on the environment that users
running the script. I'm closing this PR,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16214
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/16214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/7/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #7 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/7/consoleFull)**
for PR 16214 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #7 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/7/consoleFull)**
for PR 16214 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16214
@mengxr I think there is no (at least I did not found) concurrency issue
when multiple executors on the same machine, since native R has lock to protect
this. You can verify it by installing
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16214
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/16214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69908/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #69908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69908/consoleFull)**
for PR 16214 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #69908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69908/consoleFull)**
for PR 16214 at commit
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16214
@yanboliang What happens if there are multiple executors on the same
machine? Are there concurrency issues?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16214
Great - I think we should be careful with example code that install stuff
automatically, especially if that could run on a cluster without any change.
Perhaps we should have a blocking
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16214
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/16214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69861/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #69861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69861/consoleFull)**
for PR 16214 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16214
@felixcheung @shivaram
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #69861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69861/consoleFull)**
for PR 16214 at commit
17 matches
Mail list logo