Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-221970852
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 have this feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11033
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-221961068
+1
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-220023585
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-220023582
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-220023317
**[Test build #58775 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58775/consoleFull)**
for PR 11033 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219998704
**[Test build #58775 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58775/consoleFull)**
for PR 11033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219756852
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219756858
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219756838
**[Test build #58699 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58699/consoleFull)**
for PR 11033 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219756299
**[Test build #58699 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58699/consoleFull)**
for PR 11033 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214881768
I have the comment above about the wording on one of the sentences,
otherwise I think its fine.
---
If your project is set up for it, you can reply to this email
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214831899
@tgravescs the logging bit of the patch is in sync with master/ .
Is there anything else you want me to do regarding the documentation to get
it into a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214813942
**[Test build #57008 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57008/consoleFull)**
for PR 11033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214813952
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214813950
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-214813608
**[Test build #57008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57008/consoleFull)**
for PR 11033 at commit
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11033#discussion_r57734251
--- Diff: docs/running-on-yarn.md ---
@@ -452,3 +452,104 @@ If you need a reference to the proper location to put
log files in the YARN so t
- In
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/11033#discussion_r57308003
--- Diff: docs/running-on-yarn.md ---
@@ -452,3 +452,104 @@ If you need a reference to the proper location to put
log files in the YARN so t
- In
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/11033#discussion_r56998643
--- Diff: docs/running-on-yarn.md ---
@@ -452,3 +452,104 @@ If you need a reference to the proper location to put
log files in the YARN so t
- In
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-199824035
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-199824030
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-199823547
**[Test build #53768 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53768/consoleFull)**
for PR 11033 at commit
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11033#discussion_r56984737
--- Diff: docs/running-on-yarn.md ---
@@ -452,3 +452,104 @@ If you need a reference to the proper location to put
log files in the YARN so t
- In
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11033#discussion_r56984185
--- Diff: docs/running-on-yarn.md ---
@@ -452,3 +452,104 @@ If you need a reference to the proper location to put
log files in the YARN so t
- In
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-199773576
**[Test build #53768 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53768/consoleFull)**
for PR 11033 at commit
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-195783350
1. I'll update
2. I think the extra credential dump should be pulled up into
{{SparkHadoopUtil}}; it's not yarn-specific
---
If your project is set up for
27 matches
Mail list logo
