Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1050
---
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 enab
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-47983864
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46891710
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46891717
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16035/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879650
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879669
Merged build started.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879165
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46855913
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46855914
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16028/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46850235
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46850255
Merged build started.
---
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849805
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 h
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849779
I just checked it merges cleanly and still these test failures.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46848936
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46848937
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16026/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46847666
Merged build started.
---
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/1050#issuecomment-46847651
Merged build triggered.
---
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 h
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46339194
You are getting test failures because the patch doesn't merge cleanly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46290060
Build finished.
---
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 pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46290063
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15847/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46282247
Build triggered.
---
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46282254
Build started.
---
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 f
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46282079
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46279342
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15846/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46279341
Build finished.
---
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 pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46273865
Build started.
---
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46273855
Build triggered.
---
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 thi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46203327
Yeah, I personally prefer echoes. The indentation thing is a little hard to
track sometimes, especially because this is bash.
---
If your project is set up for it, yo
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46199870
@ScrapCodes: in that case, wouldn't it be better to just use echo
everywhere? Yeah, it's a little more verbose, but doesn't suffer from the
indentation issue.
(It
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46150946
Hi @andrewor14, added a comment about them. Not sure if we can fix them.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/1050#discussion_r13794758
--- Diff: bin/run-example ---
@@ -27,10 +27,12 @@ if [ -n "$1" ]; then
EXAMPLE_CLASS="$1"
shift
else
- echo "Usage: ./bin/run-exampl
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46054130
Hi @ScrapCodes. There are a couple of weird indentations, but other than
that this looks good.
---
If your project is set up for it, you can reply to this email and h
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1050#discussion_r13769376
--- Diff: bin/spark-class ---
@@ -38,8 +38,10 @@ if [ -z "$1" ]; then
fi
if [ -n "$SPARK_MEM" ]; then
- echo "Warning: SPARK_MEM is dep
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1050#discussion_r13769347
--- Diff: bin/run-example ---
@@ -27,10 +27,12 @@ if [ -n "$1" ]; then
EXAMPLE_CLASS="$1"
shift
else
- echo "Usage: ./bin/run-exampl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45986612
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15754/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45986611
Build finished.
---
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45982040
Hey @andrewor14, I sort of avoided EOF blocks for nested ifs, since that
can look a bit less nicer because of no indentation.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45981311
Build started.
---
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45981303
Build triggered.
---
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 thi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45921222
Also, your latest fixes use the block EOF sometimes, and multiple lines of
echo sometimes. It would be good if we could keep this consistent.
---
If your project is s
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45917646
@ScrapCodes there are alternatives if you're willing to write more code.
e.g., write the port to a separate file, or write the port with some specific
formatting and look
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45833300
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15701/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45833299
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45831447
@vanzin You are right, for now I have done the audit of all options
available. Do you have an alternative? I did not look deeply enough. Will see
if there is something
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45831423
Merged build started.
---
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/1050#issuecomment-45831420
Merged build triggered.
---
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 h
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45803346
This looks ok, but note that this isn't the only thing that can cause
pyspark to not work.
e.g. "SPARK_PRINT_LAUNCH_COMMAND=1 bin/pyspark" also fails for the same
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45787100
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45727900
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15676/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45727899
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45724609
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-45724619
Merged build started.
---
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 ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/1050
[SPARK-2109] Setting SPARK_MEM for bin/pyspark does not work.
Trivial fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1
53 matches
Mail list logo
