Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8986
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-147870089
Going to merge this now so that it doesn't become stale or get forgotten.
I'll address return code checks if the problem re-occurs once we're closer to
the release.
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145740694
Ah I see - didn't know it was failing Jenkins as well.
Code changes from rxin/spark-utils LGTM.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145672238
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145672206
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145673830
[Test build #43248 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43248/consoleFull)
for PR 8986 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145707821
[Test build #43248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43248/console)
for PR 8986 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145708102
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/8986#issuecomment-145708104
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145695189
Can we add some code here to check the return code of `make_binary_release`
? i.e. we could fail the entire release if one of the binary releases fail ?
---
If your
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8986#issuecomment-145697359
@shivaram, good idea. Note, however, that the build that was used to
publish the 0.5.1 binary releases _did_ actually fail in Jenkins.
Aside from adding
11 matches
Mail list logo
