Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6245
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-168112818
I'm going to close this pull request. If this is still relevant and you are
interested in pushing it forward, please open a new pull request. Thanks!
---
If your project i
Github user ezli commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-160249456
I will update this.
---
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 feat
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-158758320
@ezli this is pretty old now. Do you intend to update it or close it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-158689542
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 pr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122972698
[Test build #37845 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37845/console)
for PR 6245 at commit
[`1d732d0`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122944880
[Test build #37845 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37845/consoleFull)
for PR 6245 at commit
[`1d732d0`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122944562
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122944532
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122940525
[Test build #37842 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37842/console)
for PR 6245 at commit
[`827ce1e`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122940530
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122939777
[Test build #37842 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37842/consoleFull)
for PR 6245 at commit
[`827ce1e`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122937856
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-122937876
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-121072696
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104043993
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104043989
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104043951
[Test build #33162 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33162/consoleFull)
for PR 6245 at commit
[`dba6731`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104009780
[Test build #33162 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33162/consoleFull)
for PR 6245 at commit
[`dba6731`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104009191
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104009161
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 h
Github user ezli commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-104008656
@mengxr I have fixed the code style. Could you please re-run the tests?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user ezli commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103931211
@mengxr Thanks for your comments. I will check the code style.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103919443
@ezli Thanks for submitting the PR! Please follow
https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide for
code style and run `dev/lint-scala` to chec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103215556
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103215551
[Test build #33021 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33021/consoleFull)
for PR 6245 at commit
[`95db8b7`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103215553
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103215090
[Test build #33021 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33021/consoleFull)
for PR 6245 at commit
[`95db8b7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103214390
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103214443
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 have
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103214020
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
enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6245#issuecomment-103211271
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 pr
GitHub user ezli opened a pull request:
https://github.com/apache/spark/pull/6245
[MLLIB][SPARK-7615, SPARK-7617, SPARK-7618]: Avoid divided by zero norm,
cache normalized Word Vectors
1. [SPARK-7615] Commit 8c23ddd: Fix wordVectors divided by norm = 0. Add a
ScalaTest for divided
33 matches
Mail list logo
