Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14246
Merged to master, and again to 2.0 being strictly a minor doc fix.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14246
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62460/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14246
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14246
**[Test build #62460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62460/consoleFull)**
for PR 14246 at commit
[`127a428`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14246
**[Test build #62460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62460/consoleFull)**
for PR 14246 at commit
[`127a428`](https://github.com/apache/spark/commit/1
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14246
OK, especially if you've had a search for other similar latex issues. It
probably doesn't even need a JIRA but OK.
---
If your project is set up for it, you can reply to this email and have your
rep
