Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18605
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80081/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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/18605
**[Test build #80081 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80081/testReport)**
for PR 18605 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #80081 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80081/testReport)**
for PR 18605 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18605
I'll take a look
---
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
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@felixcheung Can you take a look? 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
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@yanboliang I have made changes accordingly. 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79734/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79734/testReport)**
for PR 18605 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79734/testReport)**
for PR 18605 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79728/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79728 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79728/testReport)**
for PR 18605 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79728 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79728/testReport)**
for PR 18605 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@yanboliang Thanks for your reply! I will change the unit tests now.
---
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 yanboliang commented on the issue:
https://github.com/apache/spark/pull/18605
@wangmiao1981 This is expected, see my comment
[here](https://github.com/apache/spark/pull/18613#discussion_r127011929) . This
uncovers an existing bug for ```forceIndexLabel```. I will send a
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@yanboliang after #18613, unit tests fails if "skip" is used.
For example,
data <- data.frame(clicked = base::sample(c(0, 1), 10, replace = TRUE),
someString =
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79678 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79678/testReport)**
for PR 18605 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79678/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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 user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79678 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79678/testReport)**
for PR 18605 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
Sure. I am reading the #18613 comments. Just come back from a business
travel. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
Trigger windows check.
---
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 wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
Reopen for windows check
---
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 wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@felixcheung This is a follow-up PR of JIRA-20307.
---
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79546/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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/18605
**[Test build #79546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79546/testReport)**
for PR 18605 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79546/testReport)**
for PR 18605 at commit
31 matches
Mail list logo
