Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159087029
**[Test build #46556 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46556/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092358
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159085871
Jenkins 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159091950
**[Test build #46556 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46556/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092083
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 BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159093878
No problem @jkbradley, I think this is good to go now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092086
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/9141#issuecomment-159092215
**[Test build #46555 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46555/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092353
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/9141#issuecomment-159087888
**[Test build #46555 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46555/consoleFull)**
for PR 9141 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159119395
LGTM, merging with master and branch-1.6
Thank you!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9141
---
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/9141#issuecomment-159074600
@BryanCutler Sorry for letting this go stale. Would you mind fixing the
conflicts, and we can see about getting this doc fix into 1.6? Thanks!
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149127556
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/9141#issuecomment-149124897
**[Test build #43918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43918/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149124303
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149124316
Merged build started.
---
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 BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149122916
Good point about vertical alignment. I second the latter format, it
improves the readability a little. I'll implement that here, and I wouldn't
mind doing the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149127452
**[Test build #43918 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43918/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-149127559
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9141#discussion_r42292808
--- Diff: python/pyspark/mllib/classification.py ---
@@ -594,19 +594,27 @@ def train(cls, data, lambda_=1.0):
@inherit_doc
class
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148558027
This came out of
[SPARK-10022](https://issues.apache.org/jira/browse/SPARK-10022) Scala-Python
method/parameter inconsistency check for ML during 1.5 QA
cc
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148560625
[Test build #43816 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43816/console)
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148560705
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/9141#issuecomment-148557974
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148557957
Merged build triggered.
---
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 BryanCutler opened a pull request:
https://github.com/apache/spark/pull/9141
[SPARK-10560] [PySpark] [MLlib] [Docs] Make
StreamingLogisticRegressionWithSGD Python API equal to Scala one
This is to bring the API documentation of StreamingLogisticReressionWithSGD
and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148558523
[Test build #43816 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43816/consoleFull)
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-148560703
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
29 matches
Mail list logo
