Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18164
Can one of the admins verify this patch?
---
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 feat
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18164
@ueshin, do you think it is okay to add this? I want to help review here if
so.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18164
@HyukjinKwon Yes, I think it's okay to add this.
---
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 fea
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18164
ok to test
---
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, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18164
**[Test build #77674 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77674/testReport)**
for PR 18164 at commit
[`1b3c712`](https://github.com/apache/spark/commit/1b
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18164
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/18164
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77674/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18164
**[Test build #77674 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77674/testReport)**
for PR 18164 at commit
[`1b3c712`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18164
**[Test build #77675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77675/testReport)**
for PR 18164 at commit
[`21b4f67`](https://github.com/apache/spark/commit/21
Github user rberenguel commented on the issue:
https://github.com/apache/spark/pull/18164
@ueshin @HyukjinKwon thanks for giving it a very thorough look and sorry
for my previous comment, that was terribly unclear. I was confused because the
Appveyor tick mark was green for commit 076
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18164
Ah... I see. Sorry, I misunderstood. BTW, AppVeyor only runs SparkR tests
on Windows currently.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18164
BTW, mind fixng the title/contents in the PR to be a bit more descriptive,
for example, saying "null" instead of "NA"? Not a big deal but non R guys
might get confused ...
---
If your projec
12 matches
Mail list logo