Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37681452
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13181/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37681451
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 have
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37678749
Or perhaps there's a way to check on the Input object itself whether we're
done.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37678686
Looks good but maybe make the test
`e.getMessage.toLowerCase.contains("buffer underflow")`, in case they change
the wording.
---
If your project is set up for it, you can
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37676276
Good catch, merging into master. We may want to merge this into branch-0.9
as well, @pwendell any thoughts?
---
If your project is set up for it, you can reply to this e
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37675315
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/142#issuecomment-37675314
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 hav
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/142
Don't swallow all kryo errors, only those that indicate we are out of data.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark kryoE
