Uh oh!
There was an error while loading. Please reload this page.
[BUILD] Closing some stale PRs - #15356
Conversation
HyukjinKwon
commented
Oct 5, 2016
Just to defense myself, it seems the PR such 15339 against a branch to a branch leaving a failure mark for each commit in the branches (branch-2.0). Could you please take a look please @srowen ? |
HyukjinKwon
commented
Oct 5, 2016
FYI, for 15294, the JIRA is set as |
SparkQA
commented
Oct 5, 2016
Test build #66366 has finished for PR 15356 at commit
|
HyukjinKwon
commented
Oct 5, 2016
Do you mind if I ask to confirm #12355 too? if you are uncertain, I'd like to not add it here. |
srowen
commented
Oct 5, 2016
Same thing, I think. I agree it should probably be closed but given that there's not a big hurry, I like to do the courtesy of giving at least days if not a week for someone to reply. I just put it on my big to-do list for later (FWIW I manage all this stuff with Gmail Inbox snooze / reminders and it works quite well for me, to easily "check on X and act in Y days") |
Ah, sure. I just wanted to include as many as I could as I already opened this but yes maybe I was in a hurry. I will keep it in mind. Thank you for your tip. |
## What changes were proposed in this pull request? This PR proposes to close some stale PRs and ones suggested to be closed by committer(s) or obviously inappropriate PRs (e.g. branch to branch). Closesapache#13458Closesapache#15278Closesapache#15294Closesapache#15339Closesapache#15283 ## How was this patch tested? N/A Author: hyukjinkwon <gurwls223@gmail.com> Closesapache#15356 from HyukjinKwon/closing-prs.
What changes were proposed in this pull request?
This PR proposes to close some stale PRs and ones suggested to be closed by committer(s) or obviously inappropriate PRs (e.g. branch to branch).
Closes#13458
Closes#15278
Closes#15294
Closes#15339
Closes#15283
How was this patch tested?
N/A