Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17373
Merging with master
Thanks @WeichenXu123 !
---
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 issue:
https://github.com/apache/spark/pull/17373
**[Test build #3895 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3895/testReport)**
for PR 17373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #3895 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3895/testReport)**
for PR 17373 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17373
Thanks! Will merge after rerunning tests
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17373
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/17373
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80946/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80946 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80946/testReport)**
for PR 17373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80946 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80946/testReport)**
for PR 17373 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/17373
Jenkins, 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 feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #3894 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3894/testReport)**
for PR 17373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #3894 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3894/testReport)**
for PR 17373 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17373
Oh OK makes sense. @WeichenXu123 could you please open a JIRA (linked from
this task's JIRA) and CC @felixcheung on it? Thanks!
I'll rerun tests to be safe and merge this afterwards.
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17373
We can open a JIRA to track
---
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
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/17373
@felixcheung So it do not cause bugs in sparkR, we can leave it in a
separated PR ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17373
@felixcheung How will this affect ```spark.mlp``` in R?
---
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 issue:
https://github.com/apache/spark/pull/17373
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80762/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80762 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80762/testReport)**
for PR 17373 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17373
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/17373
**[Test build #80762 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80762/testReport)**
for PR 17373 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17373
Thinking more about the proposal about separating the
classification-specific logic out of the generic Topology, it's something we
should definitely do at some point, but I'm OK with leaving it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17373
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/17373
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80689/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80689 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80689/testReport)**
for PR 17373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80689 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80689/testReport)**
for PR 17373 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/17373
Jenkins, 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 feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17373
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17373
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80684/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80684/testReport)**
for PR 17373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17373
**[Test build #80684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80684/testReport)**
for PR 17373 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/17373
cc @jkbradley Code updated, 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
30 matches
Mail list logo
