Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50694786
Jenkins, test this please. This seems like a straightforward fix - LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50695258
QA tests have started for PR 1494. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17512/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50698753
QA results for PR 1494:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50706693
Jenkins, retest 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50706728
This failed a random unit test that I would guess is unrelated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-50709274
QA results for PR 1494:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1494
---
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 maji2014 closed the pull request at:
https://github.com/apache/spark/pull/1457
---
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 maji2014 opened a pull request:
https://github.com/apache/spark/pull/1494
Required AM memory is amMem, not args.amMemory
ERROR yarn.Client: Required AM memory (1024) is above the max threshold
(1048) of this cluster appears if this code is not changed. obviously, 1024
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-49506353
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 maji2014 opened a pull request:
https://github.com/apache/spark/pull/1457
Required AM memory is amMem, not args.amMemory
ERROR yarn.Client: Required AM memory (1024) is above the max threshold
(1048) of this cluster appears if this code is not changed. obviously, 1024
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1457#issuecomment-49264180
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 maji2014 commented on the pull request:
https://github.com/apache/spark/pull/1457#issuecomment-49264699
Please focus on the second issue as the first issue is a old patch on June.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user maji2014 closed the pull request at:
https://github.com/apache/spark/pull/1457
---
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 maji2014 reopened a pull request:
https://github.com/apache/spark/pull/1457
Required AM memory is amMem, not args.amMemory
ERROR yarn.Client: Required AM memory (1024) is above the max threshold
(1048) of this cluster appears if this code is not changed. obviously, 1024
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1457#issuecomment-49391172
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 maji2014 commented on the pull request:
https://github.com/apache/spark/pull/1457#issuecomment-49391500
Please focus on second issue as title. the first Update run-example is a
old patch.
---
If your project is set up for it, you can reply to this email and have your
17 matches
Mail list logo
