Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-50853278
This seems totally reasonable, apologies for not seeing this. LGTM once
Jenkins passes.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-50853616
QA tests have started for PR 1464. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17655/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-50857070
QA results for PR 1464:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-50857152
Merging into master. Thanks!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1464
---
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 advancedxy commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-49617743
Well, could someone review this pr? Or should I close this pr?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user advancedxy commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-49416016
ping. @aarondav what do you think?
---
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 advancedxy opened a pull request:
https://github.com/apache/spark/pull/1464
[Spark 2557] fix LOCAL_N_REGEX in createTaskScheduler and make local-n and
local-n-failures consistent
[SPARK-2557](https://issues.apache.org/jira/browse/SPARK-2557)
You can merge this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-49323035
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1464#issuecomment-49390622
/cc @aarondav
---
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
10 matches
Mail list logo
