Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159021372
@zsxwing true. Fixed.
---
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159022902
LGTM pending tests.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159023678
**[Test build #46541 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46541/consoleFull)**
for PR 9853 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9853
---
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 feature is
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159011450
Since `ctx.close()` is asynchronous, this one doesn't fix the race totally.
Right?
---
If your project is set up for it, you can reply to this email and have your
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159003767
/cc @rxin @zsxwing ; we should probably get this into 1.6
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159075153
**[Test build #46541 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46541/consoleFull)**
for PR 9853 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159075319
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159075323
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159076738
Merging to master / 1.6.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158509865
**[Test build #46431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46431/consoleFull)**
for PR 9853 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158507974
Another mysterious failure where there are no failures... retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158549036
**[Test build #46431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46431/consoleFull)**
for PR 9853 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158549225
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158549222
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158245799
**[Test build #46377 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46377/consoleFull)**
for PR 9853 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158250060
**[Test build #46377 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46377/consoleFull)**
for PR 9853 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158250103
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-158250106
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/9853
[SPARK-11865] [network] Avoid returning inactive client in
TransportClientFactory.
There's a very narrow race here where it would be possible for the timeout
handler
to close a channel after
20 matches
Mail list logo
