Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5256
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93964717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93964704
[Test build #30474 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30474/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93949537
[Test build #30474 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30474/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://githu
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93948687
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 t
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93948677
Test failure looks unrelated as it's not in Python, but let me try one more
time.
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93938011
[Test build #688 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/688/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://githu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93917056
[Test build #688 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/688/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://github
Github user Sephiroth-Lin commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93915251
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 no
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93822981
[Test build #685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/685/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://githu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93805265
[Test build #685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/685/consoleFull)
for PR 5256 at commit
[`7b3c633`](https://github
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93690501
LGTM pending tests.
---
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 feat
Github user Sephiroth-Lin commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93650104
@srowen OK, thanks.
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. I
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-93366627
@Sephiroth-Lin can you rebase this? and does it make sense to refer to
"localhost" instead? Consider also that we have `Utils.localHostName()` which
is an attempt to stand
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-89242561
(Related discussion was https://github.com/apache/spark/pull/3425)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-89057245
@JoshRosen Changing the bind address to localhost is reasonable, but we
have not figured out a good way to specify local interface, `localhost` or
`127.0.0.1` both have PR
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-89049353
There was some previous discussion of localhost vs 127.0.0.1 at #3425 and I
think the conclusion there was against this change. @davies, do your comments
there about 1
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87760112
[Test build #631 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/631/consoleFull)
for PR 5256 at commit
[`c88bee9`](https://githu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87735781
[Test build #631 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/631/consoleFull)
for PR 5256 at commit
[`c88bee9`](https://github
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87735763
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 and
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87571479
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 no
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87570358
ok to test
---
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 feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5256#issuecomment-87568005
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 pro
23 matches
Mail list logo
