Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149978890
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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149990915
Jenkins, this is 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149992357
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149992387
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149995342
**[Test build #44081 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44081/consoleFull)**
for PR 9199 at commit
Github user srutis commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149978215
Sruti S
9:29 AM (4 hours ago)
to Shagun
A quick look through the source of FunctionRegistry.scala seems to
Github user shagunsodhani commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-149977083
@rxin :+1:
---
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 pull request:
https://github.com/apache/spark/pull/9199#issuecomment-150027004
Thanks - I've merged 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9199
---
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 feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-150026724
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-150026723
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9199#issuecomment-150026526
**[Test build #44081 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44081/consoleFull)**
for PR 9199 at commit
12 matches
Mail list logo