Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15936
This seems to be causing https://issues.apache.org/jira/browse/SPARK-18814
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15936
LGTM. Merging to master/2.1/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/15936
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15936
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69009/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15936
**[Test build #69009 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69009/consoleFull)**
for PR 15936 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15936
**[Test build #69009 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69009/consoleFull)**
for PR 15936 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15936
add to whitelist
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15936
ok to test
---
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
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15936
It should pick it up automatically.
---
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 nsyca commented on the issue:
https://github.com/apache/spark/pull/15936
Should I say `retest this please` to kick off the regression test?
---
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 nsyca commented on the issue:
https://github.com/apache/spark/pull/15936
The latest push (3181a08) of the PR has the following changes from its
previous version:
1. Consolidate existing checking from Analyzer.scala to CheckAnalysis.scala
2. Make use of
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/15936
I think I have contaminated the PR with some of my old code. I will push a
new PR soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15936
Can one of the admins verify this patch?
---
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
13 matches
Mail list logo
