Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64868218
Thanks. I'm merging this in master branch-1.2.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3475
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64838656
Jenkins, test this please.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64838843
[Test build #23926 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23926/consoleFull)
for PR 3475 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64842294
[Test build #23926 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23926/consoleFull)
for PR 3475 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64842297
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user maji2014 opened a pull request:
https://github.com/apache/spark/pull/3475
[SPARK-4619][Storage]delete redundant time suffix
Time suffix exists in Utils.getUsedTimeMs(startTime), no need to append
again, delete that
You can merge this pull request into a Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64530371
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
