Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189642847
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11041
---
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 the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189505699
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189505696
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189505421
**[Test build #52073 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52073/consoleFull)**
for PR 11041 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189454117
**[Test build #52073 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52073/consoleFull)**
for PR 11041 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189453748
Jenkins, test this please
---
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 mark800 commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-189189641
@srowen have rebased it.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-187681717
@mark800 thanks though this still needs a rebase
---
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 mark800 commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-187152155
@srowen Sorry for the late response, just done what you said.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-186546334
@mark800 I'll take this over if you're not able to
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184832446
Ping @mark800, can you run `./dev/test-dependencies.sh --replace-manifest`
and commit the result in order to get this patch past the build dependency test
roadblock
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184175637
@srowen I've run some simple spark SQL cases, and it doesn't seem to have
any issues.
---
If your project is set up for it, you can reply to this email and have
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184135911
Yeah, this did not update dependencies. You'll have to do that as part of
evaluating the change. This is what I meant above.
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184135540
**[Test build #51304 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51304/consoleFull)**
for PR 11041 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184135551
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184135557
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184134592
**[Test build #51304 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51304/consoleFull)**
for PR 11041 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184129034
@mark800 let's go to 0.7.4 while we're here. I agree that it doesn't look
like there are incompatible changes. But the tests would show that. Did you run
them?
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184128913
Jenkins test this please
---
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 mark800 commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184060302
@srowen It passes all the test case with version 0.7.2
No transitive deps problem in checking chill's release notes.
---
If your project is set up for it, you
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-184034549
@srowen 0.8.0 is the latest.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-183879767
@mark800 are you following up on this?
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-181015728
0.7.3 is the latest. You need to update the dependencies file before this
will pass.
Yes, good that you're looking at the release notes; what are the potential
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11041#issuecomment-178961337
Can one of the admins verify this 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
GitHub user mark800 opened a pull request:
https://github.com/apache/spark/pull/11041
[SPARK-7483] [MLlib] Upgrade Chill to 0.7.2 to support Kryo with FPGrowth
It registers more Scala classes, including ListBuffer to support Kryo with
FPGrowth.
See
26 matches
Mail list logo
