Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6952
---
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 enab
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-116804668
@yhuai yes it seems related.
@jacek-lewandowski would you mind closing this PR and opening a new one
against the master branch?
---
If your project is set up for
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-116182761
Is this one related to https://issues.apache.org/jira/browse/SPARK-8643?
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-116161226
Hey @jacek-lewandowski,
The change proposed here sounds reasonable, since spurious warnings/errors
during shutdown are really confusing to users. I'd be on-bo
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6952#discussion_r33289206
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -442,15 +442,17 @@ private[spark] class TaskSchedulerImpl(
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-115323527
This was sent against 1.3, is this not an issue on master? What about 1.4?
When that's the case, it's nice to call out explicitly that some bug only
affects some old rele
Github user sujkh85 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6952#discussion_r33277970
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -442,15 +442,17 @@ private[spark] class TaskSchedulerImpl(
sy
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6952#discussion_r33277880
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -442,15 +442,17 @@ private[spark] class TaskSchedulerImpl(
syn
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6952#discussion_r33277919
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -442,15 +442,17 @@ private[spark] class TaskSchedulerImpl(
syn
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114571117
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114571033
[Test build #35553 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35553/consoleFull)
for PR 6952 at commit
[`1963a1b`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114538201
[Test build #35553 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35553/consoleFull)
for PR 6952 at commit
[`1963a1b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114537509
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114537493
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 h
Github user jacek-lewandowski commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114537354
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 doe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114535047
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114534941
**[Test build #35548 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35548/consoleFull)**
for PR 6952 at commit
[`1963a1b`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114491702
[Test build #35548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35548/consoleFull)
for PR 6952 at commit
[`1963a1b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114489075
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-114477083
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 h
GitHub user jacek-lewandowski opened a pull request:
https://github.com/apache/spark/pull/6952
SPARK-8562: Log the lost of an executor only if SparkContext is alive
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacek-lewandowsk
21 matches
Mail list logo
