Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160217707
Thanks, @zsxwing, at least it works for my PR
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160196396
@tedyu Happy Thanksgiving, too :)
---
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 n
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10011
---
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 ena
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160195297
I saw this issue in several PR builds. I'm going to merge this one because
it only touches the test codes and it bores other people.
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160044203
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160044204
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160044154
**[Test build #46800 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46800/consoleFull)**
for PR 10011 at commit
[`82d45c9`](https://g
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160038407
Thanks for the quick fix, shixiong
Happy Thanksgiving
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160036796
**[Test build #46800 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46800/consoleFull)**
for PR 10011 at commit
[`82d45c9`](https://gi
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160036356
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160036082
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160036081
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 projec
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10011#issuecomment-160035000
cc @tdas @tedyu @andrewor14
BTW, there is a similar test in SparkListenerSuite. But SparkContext
doesn't hold a lock in `stop` method, it won't be a problem.
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/10011
[SPARK-12021][Streaming][Tests]Fix the potential dead-lock in
StreamingListenerSuite
In StreamingListenerSuite."don't call ssc.stop in listener", after the main
thread calls `ssc.stop()`, `Stream
14 matches
Mail list logo
