Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14903
Merging this into master and 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14903
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64743/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14903
**[Test build #64743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64743/consoleFull)**
for PR 14903 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14903
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/14903
**[Test build #64743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64743/consoleFull)**
for PR 14903 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14903
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
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14903
The fix is in #14904
---
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
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14903
@shivaram I see. Thanks for letting us know.
---
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
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14903
@junyangq @felixcheung The test error is due to an unrelated issue caused
when we upgraded testthat on Jenkins. I'm sending a fix for it now
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14903
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64734/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14903
**[Test build #64734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64734/consoleFull)**
for PR 14903 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14903
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/14903
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14903
**[Test build #64734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64734/consoleFull)**
for PR 14903 at commit
14 matches
Mail list logo
