Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16723
OK thanks a lot @HyukjinKwon and @wangmiao1981 !
Merging with 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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16723
(I just rebased it based on this PR and built the javadoc8 for sure. I
believe it should emit an error if this PR introduce the break but it seems
not. So, LGTM for doc changes.)
---
If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16723
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72265/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16723
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/16723
**[Test build #72265 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72265/testReport)**
for PR 16723 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16723
Ah, I fixed the others in https://github.com/apache/spark/pull/16741 Yes, I
understand it is super easy to break. So I am trying to inform committers or
frequent contributors purely as a kind
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16723
**[Test build #72265 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72265/testReport)**
for PR 16723 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16723
I delayed too! I just pushed a fix. I couldn't test it since it looks
like the Java 8 doc gen has already been broken again. (Thanks a lot for the
efforts to fix it! Btw, are you pinging the
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/16723
@jkbradley Sorry for replying late! I was out for Chinese new year this
weekend. I will check the issue mentioned by HyukjinKwon otherwise, it looks
good to me.
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16723
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72094/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16723
**[Test build #72094 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72094/testReport)**
for PR 16723 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16723
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/16723
**[Test build #72094 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72094/testReport)**
for PR 16723 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16723
@wangmiao1981 Would you mind checking this? It has small fixes I noticed
when reviewing your PR for Python LinearSVC.
---
If your project is set up for it, you can reply to this email and have
14 matches
Mail list logo
