[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-08 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16207 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 project does not have this feature

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-08 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16207 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69847/ Test FAILed. ---

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread rxin
Github user rxin commented on the issue: https://github.com/apache/spark/pull/16207 Yea i'd say in general that `--allow-empty` be there. --- 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] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/16207 Yes I have to edit the merge script to `git commit --allow-empty ...` but I don't know that we should always set it. It could prompt or something but I was too lazy to implement that.

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/16207 Sure, thanks! --- 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,

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/16207 BTW, I believe we should add `--allow-empty` when it is merged. --- 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

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread rxin
Github user rxin commented on the issue: https://github.com/apache/spark/pull/16207 For some reason I couldn't merge this one. I pushed a commit directly to master. Can you close this one now? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread rxin
Github user rxin commented on the issue: https://github.com/apache/spark/pull/16207 Merging in 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 feature enabled and wishes so, or

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16207 **[Test build #69847 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69847/consoleFull)** for PR 16207 at commit

[GitHub] spark issue #16207: [BUILD] Closing some stale/inappropriate PRs

2016-12-07 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/16207 cc @srowen Could you take a look and see if they are reasonable 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