Github user Krimit commented on the issue:
https://github.com/apache/spark/pull/18265
Cool, LGTM @jkbradley
---
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/18265
I'm going to call this ready...but please say if you see other fixes I
should make. Thanks!
Merging with master and branch-2.2
---
If your project is set up for it, you can reply to
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18265
@Krimit Thanks for taking a look! Does it look ready to merge 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 project
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18265
**[Test build #3793 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3793/testReport)**
for PR 18265 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18265
**[Test build #3793 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3793/testReport)**
for PR 18265 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18265
looks like a spurious failure, retesting
---
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/18265
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/18265
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77916/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18265
**[Test build #77916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77916/testReport)**
for PR 18265 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18265
Yep, someone hit the bug!
---
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 Krimit commented on the issue:
https://github.com/apache/spark/pull/18265
Thanks @jkbradley! I'm really curious about how this came to your
attention. Did somebody actually encounter this bug? For this bug to come up,
the model being trained would have to be truly
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18265
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77886/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18265
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/18265
**[Test build #77886 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77886/testReport)**
for PR 18265 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18265
**[Test build #77886 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77886/testReport)**
for PR 18265 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18265
CC @Krimit and @srowen who had worked on the previous related patch
---
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
16 matches
Mail list logo