Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-49479738
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 proj
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-54565274
If there's no way to reproduce this by the way, would it be okay to close
this PR? I haven't seen other people bring it up.
---
If your project is set up for it, you can r
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-54694748
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 do
Github user mathonsunday commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-55461036
It's ok to close the issue.
---
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/260#issuecomment-55462372
@mathonsunday you're the only one who can do that.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-55462913
To clarify, we don't have administrative access to this GitHub repository,
so we can't use the "Close Issue" button.
---
If your project is set up for it, you can reply
Github user mathonsunday closed the pull request at:
https://github.com/apache/spark/pull/260
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-53638507
So unfortunately I haven't been able to reproduce this, even when trying
for example to run Spark out of a symlinked directory. Did you maybe have
spaces in your path name
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-53638629
BTW if the issue is spaces, maybe we should put quotes around the second
half of this line. But unfortunately quite a few other of our scripts may be
breaking with spaces.
GitHub user mathonsunday opened a pull request:
https://github.com/apache/spark/pull/260
Fix sbt script
When I ran ./sbt/sbt assembly I got the error no such file or directory:
./sbt/sbt in both zsh and bash.
I don't know what realpath is. It's not not anything on my machin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38883549
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38883635
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 proj
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38890370
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 this
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38890368
Interesting, what OS are you on?
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38890561
Merged build triggered. Some tests failed or tests have not started
running yet.
---
If your project is set up for it, you can reply to this email and have your
re
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38890571
Merged build started. Some tests failed or tests have not started running
yet.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38893514
Merged build finished. Some tests failed or tests have not started running
yet.
---
If your project is set up for it, you can reply to this email and have your
repl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38893515
Some tests failed or tests have not started running yet.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/
Github user mathonsunday commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38938443
I'm on a Mac with OS X Mavericks
---
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
19 matches
Mail list logo