Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Alright, commit is pushed, lots of PRs are in the process of being closed.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
I'll let 10270 since the submitter is active (I'll let him close the PR if
he can't fix it). I'll take a look at 14232 since I've played with that code
(it's just a comment anyway).
---
If your
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
No, just mentioning in comments doesn't work. I'm adding the "Closes #foo"
text to the commit message I'll push, and at that time github will close them.
I'll look at adding the ones on your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14495
Does just mentioning the numbers in comments cause them to close when this
merges? I wasn't sure whether the bot or Github looks for "closes ...".
Here are some more on my list:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14495
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63230/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14495
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14495
**[Test build #63230 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63230/consoleFull)**
for PR 14495 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #9866
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #10356
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #14347
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #13248
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Also going to add #10474.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14495
**[Test build #63230 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63230/consoleFull)**
for PR 14495 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Let me know if there are any concerns.
---
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
14 matches
Mail list logo
