Github user devaraj-kavali closed the pull request at:
https://github.com/apache/spark/pull/11916
---
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
Github user devaraj-kavali commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-202318900
I have moved these changes to the PR
https://github.com/apache/spark/pull/11996 for SPARK-10530. @tgravescs, please
have a look into
Github user devaraj-kavali commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57459040
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57369488
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
//
Github user devaraj-kavali commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57349258
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57342982
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
//
Github user devaraj-kavali commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57340394
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/11916#discussion_r57316516
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -620,6 +620,14 @@ private[spark] class TaskSetManager(
//
Github user devaraj-kavali commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200740334
Thanks @rxin and @andrewor14 for looking into the patch.
These failed tests in the latest build are not related to this patch and
they have been failing
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200738785
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/11916#issuecomment-200738781
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/11916#issuecomment-200738616
**[Test build #54016 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54016/consoleFull)**
for PR 11916 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200698229
**[Test build #54016 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54016/consoleFull)**
for PR 11916 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200690718
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/11916#issuecomment-200690724
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/11916#issuecomment-200690703
**[Test build #54009 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54009/consoleFull)**
for PR 11916 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200690203
**[Test build #54009 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54009/consoleFull)**
for PR 11916 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200679647
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/11916#issuecomment-200679645
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/11916#issuecomment-200679249
**[Test build #53998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53998/consoleFull)**
for PR 11916 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200643122
**[Test build #53998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53998/consoleFull)**
for PR 11916 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200641412
ok to test
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200607117
cc @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 this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200325537
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 devaraj-kavali opened a pull request:
https://github.com/apache/spark/pull/11916
[SPARK-13343] [CORE] speculative tasks that didn't commit shouldn't be
marked as success
## What changes were proposed in this pull request?
Now with this patch, killed tasks will
25 matches
Mail list logo
