Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@shivaram @felixcheung thanks for the reviews. Will keep the feedbacks in
mind.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14179
LGTM.
btw, for future references, you could either
```
# sep defaults to " "
paste("sparkPackages has no effect when using spark-submit or sparkR
shell,",
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14179
LGTM.
---
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 fe
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@felixcheung @shivaram Is the current state okay?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62425/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62425 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62425/consoleFull)**
for PR 14179 at commit
[`12bd700`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62424/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62424 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62424/consoleFull)**
for PR 14179 at commit
[`aefdb45`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
**[Test build #62425 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62425/consoleFull)**
for PR 14179 at commit
[`12bd700`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62424 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62424/consoleFull)**
for PR 14179 at commit
[`aefdb45`](https://github.com/apache/spark/commit/a
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14179
A couple of test files are reusing an existing SparkSession/SparkContext by
calling `sparkR.sparkContext` I think they are now hitting the warning
statement that is added in this PR, somehow. I'
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62414/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
**[Test build #62414 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62414/consoleFull)**
for PR 14179 at commit
[`b425540`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62414 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62414/consoleFull)**
for PR 14179 at commit
[`b425540`](https://github.com/apache/spark/commit/b
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14179
@krishnakalyan3 We don't need to modify the message. You can keep the
original message and just split it across two lines with something like the
`paste` function used in
https://github.com/apache
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@felixcheung @shivaram I am not sure if the warning message is clear
enough. I did the best I could with character limit of 100. I am not sure which
SparkR unit tests fail from the logs below
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62410/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62410 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62410/consoleFull)**
for PR 14179 at commit
[`204fa25`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
**[Test build #62410 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62410/consoleFull)**
for PR 14179 at commit
[`204fa25`](https://github.com/apache/spark/commit/2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62409 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62409/consoleFull)**
for PR 14179 at commit
[`c0dca31`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62409/
Test FAILed.
---
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@felixcheung my local unit test still fail, anyway thanks for the
clarification.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62409 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62409/consoleFull)**
for PR 14179 at commit
[`c0dca31`](https://github.com/apache/spark/commit/c
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14179
The error in the link you provided
(https://gist.github.com/krishnakalyan3/6585a1007b731e82fede1b942ea00bec) are
odd, I have not seen them. What is the version of testthat you have installed?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62385/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62385 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62385/consoleFull)**
for PR 14179 at commit
[`76fa14b`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62385 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62385/consoleFull)**
for PR 14179 at commit
[`76fa14b`](https://github.com/apache/spark/commit/7
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@shivaram @felixcheung My patch fails spark unit test. (./R/run-tests.sh)
Logs https://gist.github.com/krishnakalyan3/6585a1007b731e82fede1b942ea00bec
I am not sure how to go about reso
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62338/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
**[Test build #62338 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62338/consoleFull)**
for PR 14179 at commit
[`259c4af`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62338 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62338/consoleFull)**
for PR 14179 at commit
[`259c4af`](https://github.com/apache/spark/commit/2
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62254/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62254 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62254/consoleFull)**
for PR 14179 at commit
[`3d5d49b`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62254 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62254/consoleFull)**
for PR 14179 at commit
[`3d5d49b`](https://github.com/apache/spark/commit/3
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14179
Jenkins, 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,
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
cc @shivaram
---
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/14179
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
45 matches
Mail list logo
