Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13608
Merged to master/2.0
---
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,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13608
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60313/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13608
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/13608
**[Test build #60313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60313/consoleFull)**
for PR 13608 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13608
Actually, at this time, I manually clicked all the link in mllib
documentation. Maybe, later, we can make some simple crawler to check this kind
of errors.
---
If your project is set up for
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13608
Yep. I already built this with Jekyll locally and checked the result
manually, too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13608
Thank you for fast review, @srowen .
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/13608
Seems OK, if you were able to spot check that the new links are now fixed
in the compiled docs output HTML.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13608
**[Test build #60313 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60313/consoleFull)**
for PR 13608 at commit
