Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14759
Merging this to master, branch-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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64243/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
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/14759
**[Test build #64243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64243/consoleFull)**
for PR 14759 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64243/consoleFull)**
for PR 14759 at commit
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
ah never mind, just saw the log. Thanks @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
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
I see. Perhaps we can put that in the document somewhere if not yet? Does
Jenkins run check-cran under branch 2.0 or it uses no-test?
---
If your project is set up for it, you can reply to this
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14759
I merged #14734 - that should help to avoid chasing down more warning
that's failing the test
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14759
So running `R/check-cran.sh` out of the box on master branch will fail.
However if you run `NO_TESTS=1 R/check-cran.sh` it should pass. Basically we
can't use check-cran.sh to run unit tests on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64241/
Test FAILed.
---
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
I see. Thanks for the clarification.
My concern is somewhat unrelated to this update. If we work under master
branch and then run cran-check, it will fail right? Or did I misunderstand
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64241/consoleFull)**
for PR 14759 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14759
The new check I added doesn't run unit tests using `R CMD check`-- it only
checks the documentation etc. and thus works on the master branch as well.
---
If your project is set up for it, you
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
SGTM. One other thing is we can only run this test under branch-2.0 right?
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64241/consoleFull)**
for PR 14759 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14759
@junyangq I guess we could - but it should be pretty simple to figure out
what is the problem given the entire log file ? FWIW the error we have right
now will be fixed when we merge #14734
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64237 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64237/consoleFull)**
for PR 14759 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64237/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14759
Would it be useful to pick out the specific errors and warnings?
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64237/consoleFull)**
for PR 14759 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64228/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64228 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64228/consoleFull)**
for PR 14759 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64228 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64228/consoleFull)**
for PR 14759 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64224 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64224/consoleFull)**
for PR 14759 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14759
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64224/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14759
**[Test build #64224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64224/consoleFull)**
for PR 14759 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14759
cc @felixcheung @junyangq
---
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
33 matches
Mail list logo
