Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
It seems fine now. Closing 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 feature
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
Oh, it seems 3.3.1 is just right now released for Windows as well. It seems
fine now - https://ci.appveyor.com/project/spark-test/spark/build/45-test1122
I will close this if the tests pass
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
Oh wait. Please do not merge 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 feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15709
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67867/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15709
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 shivaram commented on the issue:
https://github.com/apache/spark/pull/15709
Yeah I'm fine with fixing a version - but as you said its sometimes helpful
to find if we have some problems with a newly released R version. But yeah we
should have a stable download URL
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15709
**[Test build #67867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67867/consoleFull)**
for PR 15709 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
I see. That seems nice too but I hope the version is fixed if this one is
also fine too..
I am worried if the version is suddenly bumped up and some tests are failed
(at least, I was a
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/15709
This approach is fine - The other thing we could do is just use the latest
stable version as described in https://cloud.r-project.org/bin/windows/base/ -
If you see the link at the bottom it says
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
(cc @nchammas too who I also guess met this issue first. I would like to
let him know.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
Maybe, I might create a JIRA to describe the known issues with AppVeyor.
(does it make sense?)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15709
**[Test build #67867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67867/consoleFull)**
for PR 15709 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
cc @felixcheung, @shivaram, @srowen and @wangmiao1981 (who I believe met
this issue first).
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
Build started: [SparkR] `ALL`
14 matches
Mail list logo
