[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

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

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

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

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15198 **[Test build #65767 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65767/consoleFull)** for PR 15198 at commit [`f796507`](https://github.com/apache/spark/commit/

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/15198 Thanks, I just updated them. --- 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 an

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/15198 Agree, and I would add: 9440 15023 14643 14827 --- 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 fea

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15198 **[Test build #65767 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65767/consoleFull)** for PR 15198 at commit [`f796507`](https://github.com/apache/spark/commit/f

[GitHub] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/15198 I don't mind closing this if they are so few. cc @srowen --- 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] spark issue #15198: [BUILD] Closes some stale PRs

2016-09-22 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/15198 I might have to propose this later after queuing up those more; however, it seems some PRs against a branch to a branch such as 15118, 15184 and 15183 are triggering AppVeyor tests, leaving a fa