Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76316/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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/17783
**[Test build #76316 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76316/testReport)**
for PR 17783 at commit
[`f44aa74`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76316 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76316/testReport)**
for PR 17783 at commit
[`f44aa74`](https://github.com/apache/spark/commit/f4
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
I'm surprised `@name %<=>%` does too
---
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
en
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
Huh, seems to work after all.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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/17783
**[Test build #76314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76314/testReport)**
for PR 17783 at commit
[`99f8dd2`](https://github.com/apache/spark/commit/9
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76314/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76314/testReport)**
for PR 17783 at commit
[`99f8dd2`](https://github.com/apache/spark/commit/99
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
> didn't it warn about @rdname column being lower cased?
We use lower case `column` as `@rdname` for both `column` and
`Column-class` so it is OK. We just have both in the same output file
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
didn't it warn about `@rdname column` being lower cased? Not sure how later
tests are passing.
what if we change both `@rdname` and `@name`?
```
#' @rdname not
#' @name not
``
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
In short, depending on how you set `@rdname` and `@name` we get warnings
```
`prepare_Rd: not.Rd: \name should not contain !`
```
or
```
Undocumented S4 methods:
g
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
Sounds good - I didn't look very closely - what's the issue with ! doc
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
> we could try but the number of methods and examples we have is much?
higher than a lot of other packages
Yeah... Maybe it is possible to hack docs generation process instead. Leave
`\
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
> I wonder if we could actually remove \dontrun, push sparkR.session into
\dontshow and still keep inside the CRAN time limits...
we could try but the number of methods and examples we h
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
is this ready? please remove the `[WIP]` in the title
---
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 hav
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76295/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76295 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76295/testReport)**
for PR 17783 at commit
[`457b9c2`](https://github.com/apache/spark/commit/4
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76295 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76295/testReport)**
for PR 17783 at commit
[`457b9c2`](https://github.com/apache/spark/commit/45
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
Jenkins retest 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 and wis
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76291/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76291/testReport)**
for PR 17783 at commit
[`457b9c2`](https://github.com/apache/spark/commit/4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76290/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76290 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76290/testReport)**
for PR 17783 at commit
[`f83bcbd`](https://github.com/apache/spark/commit/f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76291/testReport)**
for PR 17783 at commit
[`457b9c2`](https://github.com/apache/spark/commit/45
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76290/testReport)**
for PR 17783 at commit
[`f83bcbd`](https://github.com/apache/spark/commit/f8
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76285/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76285/testReport)**
for PR 17783 at commit
[`a0c9222`](https://github.com/apache/spark/commit/a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76285/testReport)**
for PR 17783 at commit
[`a0c9222`](https://github.com/apache/spark/commit/a0
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76282/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76282/testReport)**
for PR 17783 at commit
[`1788d6f`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76282/testReport)**
for PR 17783 at commit
[`1788d6f`](https://github.com/apache/spark/commit/17
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76281/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76281/testReport)**
for PR 17783 at commit
[`3004310`](https://github.com/apache/spark/commit/3
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76281/testReport)**
for PR 17783 at commit
[`3004310`](https://github.com/apache/spark/commit/30
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76280/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76280/testReport)**
for PR 17783 at commit
[`dc7c3dd`](https://github.com/apache/spark/commit/d
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/17783
OK, let's remove example output for now and leave `lintr` issues for
another day.
I wonder if we could actually remove `\dontrun`, push `sparkR.session` into
`\dontshow` and still keep ins
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76280/testReport)**
for PR 17783 at commit
[`dc7c3dd`](https://github.com/apache/spark/commit/dc
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76279/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76279 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76279/testReport)**
for PR 17783 at commit
[`47c4b41`](https://github.com/apache/spark/commit/4
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76279/testReport)**
for PR 17783 at commit
[`47c4b41`](https://github.com/apache/spark/commit/47
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17783
Interesting, I think we got 0.2 from his github
https://github.com/jimhester/lintr
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76237/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76237 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76237/testReport)**
for PR 17783 at commit
[`a443a84`](https://github.com/apache/spark/commit/a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76237/testReport)**
for PR 17783 at commit
[`a443a84`](https://github.com/apache/spark/commit/a4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76235 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76235/testReport)**
for PR 17783 at commit
[`39c9720`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76235/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76235/testReport)**
for PR 17783 at commit
[`39c9720`](https://github.com/apache/spark/commit/39
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76226/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17783
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76226 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76226/testReport)**
for PR 17783 at commit
[`79857c9`](https://github.com/apache/spark/commit/7
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17783
**[Test build #76226 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76226/testReport)**
for PR 17783 at commit
[`79857c9`](https://github.com/apache/spark/commit/79
64 matches
Mail list logo
