Github user JoshRosen closed the pull request at:
https://github.com/apache/spark/pull/8912
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143871541
For some context, the reason that I want to move these classes is because
it would be nice to integrate the TaskMemoryManager and ExecutorMemoryManager
with other
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143190405
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/8912#issuecomment-143190406
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/8912#issuecomment-143190324
[Test build #43018 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43018/console)
for PR 8912 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143149940
As long as use of unsafe can still be turned off and is still pretty
'private' inside core, seems like it doesn't change much.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143161248
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143161232
Merged build triggered.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143161069
retest 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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143162410
[Test build #43018 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43018/consoleFull)
for PR 8912 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143097261
[Test build #42999 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42999/consoleFull)
for PR 8912 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143097556
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143097550
[Test build #42999 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42999/console)
for PR 8912 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143097558
Test FAILed.
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/8912#issuecomment-143095938
Merged build started.
---
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 JoshRosen opened a pull request:
https://github.com/apache/spark/pull/8912
[SPARK-10822] Move contents of spark-unsafe subproject into spark-core
As a pre-requisite to other memory-management changes, I think that we
should move the contents of the spark-unsafe
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143095898
/cc @rxin @andrewor14
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143095916
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096907
Merged build started.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096865
Jenkins, retest 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096893
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143099710
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143099698
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096623
[Test build #42998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42998/consoleFull)
for PR 8912 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096771
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096769
[Test build #42998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42998/console)
for PR 8912 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096772
Test FAILed.
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/8912#issuecomment-143101279
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/8912#issuecomment-143101280
Test FAILed.
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/8912#issuecomment-143120102
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/8912#issuecomment-143120106
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/8912#issuecomment-143119970
[Test build #43002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43002/console)
for PR 8912 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143096352
LGTM
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143099262
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143099242
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143100376
[Test build #43002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43002/consoleFull)
for PR 8912 at commit
36 matches
Mail list logo
