Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13527
LGTM bar one tiny nit. Also, the title should probably say "yarn" instead
of "core" since this only really affects YARN mode.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60579/consoleFull)**
for PR 13527 at commit
Github user nezihyigitbasi commented on the issue:
https://github.com/apache/spark/pull/13527
@vanzin makes sense, updated.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60577/consoleFull)**
for PR 13527 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13527
@nezihyigitbasi I went through the change again and I think the code should
be a little more careful about only looking at the YARN settings if actually
running on YARN.
You could also make
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13527
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13527
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60514/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60514 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60514/consoleFull)**
for PR 13527 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13527
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13527
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60513/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60513 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60513/consoleFull)**
for PR 13527 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60514 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60514/consoleFull)**
for PR 13527 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13527
LGTM pending tests. The 2.10 shell code could be cleaned up, but that would
be better done as part of removing `ADD_JARS`.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13527
**[Test build #60513 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60513/consoleFull)**
for PR 13527 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13527
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 have this feature
enabled and wishes so, or if the
Github user nezihyigitbasi commented on the issue:
https://github.com/apache/spark/pull/13527
thanks @vanzin, addressed your comments.
---
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 nezihyigitbasi commented on the issue:
https://github.com/apache/spark/pull/13527
@vanzin updated to address your comments.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13527
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 project does not have this
18 matches
Mail list logo
