Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13581
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60247/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13581
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/13581
**[Test build #60247 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60247/consoleFull)**
for PR 13581 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60245/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13581
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/13581
**[Test build #60245 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60245/consoleFull)**
for PR 13581 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13581
LGTM, pending jenkins
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13581
> in the PR description
@hvanhovell not PR title...
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13581
**[Test build #60247 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60247/consoleFull)**
for PR 13581 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/13581
Tip: if you put "closes #13522" in the PR description then the subsumed PR
will be automatically closed once this PR is merged.
---
If your project is set up for it, you can reply to this email
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13581
LGTM except a minor comment
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13581
**[Test build #60245 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60245/consoleFull)**
for PR 13581 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/13581
cc @cloud-fan
---
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,
14 matches
Mail list logo