Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #79940 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79940/testReport)**
for PR 18663 at commit
[`56abc80`](https://github.com/apache/spark/commit/56
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #79940 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79940/testReport)**
for PR 18663 at commit
[`56abc80`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79940/
Test PASSed.
---
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18663
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 feature
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #80085 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80085/testReport)**
for PR 18663 at commit
[`56abc80`](https://github.com/apache/spark/commit/56
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #80085 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80085/testReport)**
for PR 18663 at commit
[`56abc80`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80085/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18663
Merging 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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18663
FYI, I started by trying to clean up the referenced PR but ended up pretty
much re-writing it...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #79692 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79692/testReport)**
for PR 18663 at commit
[`1496b78`](https://github.com/apache/spark/commit/14
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18663
**[Test build #79692 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79692/testReport)**
for PR 18663 at commit
[`1496b78`](https://github.com/apache/spark/commit/1
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79692/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18663
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18663
@tgravescs @jerryshao
---
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
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18663
LGTM, I tried it locally, looks now executors can be ramped up soon after
AM restart.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18663
I haven't had a chance to look at this yet, but this doesn't by chance fix
the allocator re-evaluating if it needs executors all the time does it?
I have seen issues where executors can id
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18663
That sounds like a different issue. I've seen @squito debugging issues that
sound similar to that, not sure if he got down to making any scheduler changes.
---
If your project is set up for it, you
19 matches
Mail list logo
