Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7152
---
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 enab
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117746861
LGTM. Thanks @sun-rui for this change !
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117641998
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117641935
[Test build #36251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36251/console)
for PR 7152 at commit
[`8ad2440`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117638898
[Test build #36251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36251/consoleFull)
for PR 7152 at commit
[`8ad2440`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117638656
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117623014
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117507600
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117507538
[Test build #36238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36238/console)
for PR 7152 at commit
[`8fe9f0c`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117500541
[Test build #36238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36238/consoleFull)
for PR 7152 at commit
[`8fe9f0c`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117500377
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7152#issuecomment-117500364
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 h
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/7152
[SPARK-7714][SPARKR] SparkR tests should use more specific expectations
than expect_true
1. Update the pattern 'expect_true(a == b)' to 'expect_equal(a, b)'.
2. Update the pattern 'expect_true(i
13 matches
Mail list logo
