Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18152
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 feature
enabled and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77728/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77728 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77728/testReport)**
for PR 18152 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77728 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77728/testReport)**
for PR 18152 at commit
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/18152
@srowen Thanks for pointing that out. Btw, I reviewed all calls of
broadcast in ml again and found this instance also happens in `LDAModel.scala`.
I think now all broadcasted objects in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77618/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77618 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77618/testReport)**
for PR 18152 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77618 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77618/testReport)**
for PR 18152 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18152
Yes, I agree with that. It looks like there may be a similar instance in
`GradientDescent.scala`, where `bcWeights` is used in a `treeAggregate` but
then never destroyed.
In every other
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77570/testReport)**
for PR 18152 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18152
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77570/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18152
**[Test build #77570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77570/testReport)**
for PR 18152 at commit
15 matches
Mail list logo