Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181774605
**[Test build #50964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50964/consoleFull)**
for PR 1 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181800060
**[Test build #50964 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50964/consoleFull)**
for PR 1 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181800643
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/1#issuecomment-181800638
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181823866
Merged to master
---
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181537630
This looks good to me, and it looks like we synchronize on the same object
that the deprecated SynchronizedQueue did so it should still be ok for peoples
code that was
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181538552
Agreed, I also just compared it with the SynchronizedQueue sources and
behaviour should be identical. looks good
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181028045
**[Test build #50903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50903/consoleFull)**
for PR 1 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181039154
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/1#issuecomment-181039155
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-181039108
**[Test build #50903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50903/consoleFull)**
for PR 1 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1#discussion_r52118737
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/InputStreamsSuite.scala ---
@@ -66,7 +65,7 @@ class InputStreamsSuite extends TestSuiteBase
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/1
[SPARK-13170] [STREAMING] Investigate replacing SynchronizedQueue as it is
deprecated
Replace SynchronizeQueue with synchronized access to a Queue
You can merge this pull request into a Git
14 matches
Mail list logo
