Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15686
Thank you for merging, @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 have this feature
enab
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15686
Merged to 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 i
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15686
Never mind, @HyunjinKwon .
I was also curious about AppVoyer failure. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
@dongjoon-hyun I am sorry for unrelated comments here. All these comments
are not related with this PR.
@shivaram Sure, Let me try to create a JIRA. I will cc you. We might be
able to t
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/15686
Yeah I think it'll be a good idea to know the error rate we hit.
@HyukjinKwon It might also be good to create an INFRA ticket to see if we can
re-trigger the AppVeyor builds something
---
If your
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
There are three problems with it.
- it starts the build when someone merges the latest upstream (not rebases)
when pushing more commits in its PR (as the merged one usually has the chang
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15686
This change seems fine.
If Appveyor is encountering errors regularly, we might consider disabling
it, just because it wouldn't be giving useful information if most failures were
spurious.
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
I believe the message indicates the same case with the PR 15673 but it
seems spurious in this case.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
@rxin, it seems spurious. The message seems meaning the failure when the
commit is virtually not mergeable[1].
It seems it fails time to time for various reasons. For example, in some
c
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15686
@HyukjinKwon why are the appveyor checks failing?
---
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 user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
Build started: [SparkR] `ALL`
[](https://ci.appveyor.com/proje
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15686
Thank you for review and approval, @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 have this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15686
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67782/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15686
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 user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15686
**[Test build #67782 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67782/consoleFull)**
for PR 15686 at commit
[`b385a4c`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15686
**[Test build #67782 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67782/consoleFull)**
for PR 15686 at commit
[`b385a4c`](https://github.com/apache/spark/commit/b
16 matches
Mail list logo
