Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-74217801
Test PASSed.
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/4522#issuecomment-74217797
[Test build #27420 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27420/consoleFull)
for PR 4522 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24680952
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -40,6 +40,7 @@ import org.apache.ivy.plugins.resolver.{ChainResolver,
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-74294528
Merged into master and 1.3 after fixing the comments myself. I realize that
the neighboring functions also do not have the correct return type so I added
those too.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4522
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24680879
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -89,6 +90,17 @@ object SparkSubmit {
printStream.println(Run with
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-74173008
LGTM if the behavior of `-v` is reverted.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-74172115
Yeah we cannot change the behavior of `-v`, though we could also print the
version in the usage message.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-74212015
[Test build #27420 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27420/consoleFull)
for PR 4522 at commit
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24495488
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24478679
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24478804
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24492501
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24490981
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4522#discussion_r24491713
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -413,10 +413,13 @@ private[spark] class SparkSubmitArguments(args:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-73838659
[Test build #27274 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27274/consoleFull)
for PR 4522 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-73838664
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user uncleGen commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-73839883
An irrelevant test failure in `DirectKafkaStreamSuite` introduced by
[PR](4384)
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/4522
[SPARK-5732][CORE]:Add an option to print the spark version in spark script.
Naturally, we need to add an option to print the spark version in spark
script. It is pretty common in script tool.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4522#issuecomment-73835711
[Test build #27274 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27274/consoleFull)
for PR 4522 at commit
20 matches
Mail list logo
