Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10337
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165851533
Merging 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165537658
**[Test build #47937 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47937/consoleFull)**
for PR 10337 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165532819
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 this
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165570393
Solved for me too now
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165551157
There's no failure anywhere; we're just logging exceptions that shouldn't
necessarily be logged.
---
If your project is set up for it, you can reply to this email and
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165568827
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165603507
**[Test build #47937 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47937/consoleFull)**
for PR 10337 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165603682
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165603677
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165605204
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165607496
**[Test build #47958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47958/consoleFull)**
for PR 10337 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165549701
@vanzin So, the problem is that we log the error that should not be logged
instead of we fail to code-gen?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165628654
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165628655
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/10337#issuecomment-165628558
**[Test build #47958 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47958/consoleFull)**
for PR 10337 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165246287
**[Test build #47854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47854/consoleFull)**
for PR 10337 at commit
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/10337
[SPARK-12350] [core] Don't log errors when requested stream is not found.
If a client requests a non-existent stream, just send a failure message
back, without logging any error on the server
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165266841
Unfortunatly I now get another, similar error message in spark-shell
```
15/12/16 14:00:48 ERROR NettyRpcEnv: Error downloading stream
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165284577
Sorry to bother you again, there is one more error message that appears.
This can be fixed by changing
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165292856
I'm running the code snippet from the original JIRA:
```scala
import org.apache.spark.ml.feature.VectorAssembler
val df = sc.parallelize(List((1,2),
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165280738
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165280736
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165280610
**[Test build #47854 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47854/consoleFull)**
for PR 10337 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165276262
Hmm, I did not notice that when testing, but will clean it up.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165278452
**[Test build #47860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47860/consoleFull)**
for PR 10337 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165287631
Hmm, that one shouldn't just be a log change. What's the code you're
running to actually hit that?
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165302278
**[Test build #47860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47860/consoleFull)**
for PR 10337 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165303744
I was running in local-cluster mode, I think that's why I was not seeing
the executor-side log. Let me see if I can get rid of it easily.
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165322377
**[Test build #47875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47875/consoleFull)**
for PR 10337 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165322520
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165322516
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165303353
> Hmm, that one shouldn't just be a log change. What's the code you're
running to actually hit that?
The problem here is there is no special exception for not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165302377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165302376
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10337#issuecomment-165309352
**[Test build #47875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47875/consoleFull)**
for PR 10337 at commit
36 matches
Mail list logo
