Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14425
Done, see https://github.com/apache/spark/pull/14427
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14425
@ericl there is a conflict with branch-2.0. Can you create a pull request
for 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 wel
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14425
Merging in master/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
enabled and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14425
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63047/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14425
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/14425
**[Test build #63047 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63047/consoleFull)**
for PR 14425 at commit
[`a254540`](https://github.com/apache/spark/commit/
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14425
Yep, both fail prior to the fix.
On Sat, Jul 30, 2016, 3:32 PM Reynold Xin wrote:
> LGTM (assuming the test case would fail without the fix)
>
> â
> You are receiving th
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14425
LGTM (assuming the test case would fail without the fix)
---
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 th
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14425
**[Test build #63047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63047/consoleFull)**
for PR 14425 at commit
[`a254540`](https://github.com/apache/spark/commit/a