Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
There are conflicts with 2.0. #15646 is the backport for 2.0.
---
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
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
Thanks! Merging to master and 2.0.
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/15520
lgtm
---
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/15520
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/15520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67461/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67461 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67461/consoleFull)**
for PR 15520 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67461/consoleFull)**
for PR 15520 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15520
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/15520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67112/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67112/consoleFull)**
for PR 15520 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67112/consoleFull)**
for PR 15520 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
cc @andrewor14
---
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/15520
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/15520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67094/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67094 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67094/consoleFull)**
for PR 15520 at commit
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15520
> Yes, I think so. It just needs more lines :)
I think the solution you propose is sound. Do you think that a quick
mention about avoiding the `BlockingContext` in a comment would help in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67094 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67094/consoleFull)**
for PR 15520 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
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 wishes so,
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
> Would installing a custom BlockingContext on threads that run tasks also
work?
Yes, I think so. It just needs more lines :)
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15520
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/15520
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67088/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67088 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67088/consoleFull)**
for PR 15520 at commit
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15520
That makes sense, thanks for explaining. Would installing a custom
`BlockingContext` on threads that run tasks also work? I'm not very familiar
with the internals of the Awaitable api so I'm just
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15520
> Is it to avoid the blocking() call in Await?
Yep.
---
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 jodersky commented on the issue:
https://github.com/apache/spark/pull/15520
I'm not sure I completely understand why you have to use `Awaitable`
instead of `Await`. Is it to avoid the [`blocking()` call in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15520
**[Test build #67088 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67088/consoleFull)**
for PR 15520 at commit
26 matches
Mail list logo
