Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10890
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176121885
Merged to master
---
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 featu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176115335
**[Test build #50271 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50271/consoleFull)**
for PR 10890 at commit
[`73bf7e9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176115460
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176115457
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176109173
**[Test build #50271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50271/consoleFull)**
for PR 10890 at commit
[`73bf7e9`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-176104639
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-175517012
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-175517006
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 projec
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-175508971
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 t
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-175509029
LGTM
---
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 a
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10890#discussion_r50671889
--- Diff: docs/submitting-applications.md ---
@@ -177,8 +177,9 @@ debugging information by running `spark-submit` with
the `--verbose` option.
# Ad
Github user jimlohse commented on a diff in the pull request:
https://github.com/apache/spark/pull/10890#discussion_r50653981
--- Diff: docs/submitting-applications.md ---
@@ -177,8 +177,9 @@ debugging information by running `spark-submit` with
the `--verbose` option.
#
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10890#discussion_r50640513
--- Diff: docs/submitting-applications.md ---
@@ -177,8 +177,9 @@ debugging information by running `spark-submit` with
the `--verbose` option.
# Ad
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-174331990
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 p
GitHub user jimlohse reopened a pull request:
https://github.com/apache/spark/pull/10890
Provide same info as in spark-submit --help
this is stated for --packages and --repositories. Without stating it for
--jars, people expect a standard java classpath to work, with expansion and
Github user jimlohse closed the pull request at:
https://github.com/apache/spark/pull/10890
---
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 e
Github user jimlohse commented on the pull request:
https://github.com/apache/spark/pull/10890#issuecomment-174331816
I don't know if I have write access, about to find out, I suspect I don't.
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user jimlohse opened a pull request:
https://github.com/apache/spark/pull/10890
Provide same info as in spark-submit --help
this is stated for --packages and --repositories. Without stating it for
--jars, people expect a standard java classpath to work, with expansion and
us
19 matches
Mail list logo
