Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67419464
ok to test
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67419469
add to whitelist
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67419474
test 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67419858
[Test build #24561 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24561/consoleFull)
for PR 3685 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67423199
LGTM. Waiting for Jenkins ...
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67423321
LGTM, thanks!
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67425078
@Lewuathe I believe there are 2 more tags to fix (1 more DeveloperAPI and
1 more WARN tag) in those same files. (Thanks!)
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67427413
[Test build #24561 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24561/consoleFull)
for PR 3685 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67427419
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67428216
Oops, I was wrong. LGTM
Thanks!
---
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67428413
Merged into master. Thanks!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3685
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-67083774
@Lewuathe Thanks for the PR! As long as you're fixing those, would you
mind fixing the 2 DeveloperApi tags in pyspark/mllib/feature.py and the 2
WARN tags in
GitHub user Lewuathe opened a pull request:
https://github.com/apache/spark/pull/3685
[SPARK-4822] Use sphinx tags for Python doc annotations
Modify python annotations for sphinx. There is no change to build process
from.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3685#issuecomment-66769232
Can one of the admins verify this patch?
---
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
15 matches
Mail list logo
