Github user CodingCat closed the pull request at:
https://github.com/apache/spark/pull/637
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60384224
[Test build #22135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22135/consoleFull)
for PR 637 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60397461
[Test build #22140 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22140/consoleFull)
for PR 637 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60400332
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/637#issuecomment-60400326
**[Test build #22135 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22135/consoleFull)**
for PR 637 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60408209
Test PASSed.
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/637#issuecomment-60408198
[Test build #22140 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22140/consoleFull)
for PR 637 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60451786
[Test build #22165 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22165/consoleFull)
for PR 637 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60456700
[Test build #22165 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22165/consoleFull)
for PR 637 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60456705
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/637#issuecomment-60457069
[Test build #22174 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22174/consoleFull)
for PR 637 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-60461100
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/637#issuecomment-60461092
[Test build #22174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22174/consoleFull)
for PR 637 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-58754084
ping
---
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
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-58754089
ping
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-51286714
QA tests have started for PR 637. This patch DID NOT merge cleanly!
brView progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17976/consoleFull
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-51287642
rebased the patchjust curiouswho triggered the test?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-51287929
QA tests have started for PR 637. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17981/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-51287934
QA results for PR 637:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-51290473
QA results for PR 637:br- This patch PASSES unit tests.brbrFor more
information see test
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-50057749
This rebases cleanly on top of https://github.com/apache/spark/pull/1561,
so let's get that one in first.
---
If your project is set up for it, you can reply to this
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-49745118
ping.
---
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-49094948
ping...
---
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/637#issuecomment-46598616
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/637#issuecomment-46598627
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/637#issuecomment-46603500
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46603503
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15916/
---
If your project
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46603720
finally MIMA accepts the 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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46115672
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/637#issuecomment-46115677
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/637#issuecomment-46116617
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15805/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46116616
Merged build finished.
---
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/637#issuecomment-46103789
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/637#issuecomment-46103786
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/637#issuecomment-46104438
Merged build finished.
---
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/637#issuecomment-46104439
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15796/
---
If your project is set up for it, you can
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46104739
what does this mean?
```
[error] * method
dagScheduler_=(org.apache.spark.scheduler.DAGScheduler)Unit in class
org.apache.spark.SparkContext does not have
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46104906
It means that the check for binary compatibility after your patch is
applied has failed because the checker thinks that there previously was a
default/automatic
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46105020
I seethank you for the hints!
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46105175
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/637#issuecomment-46105177
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/637#issuecomment-46105640
Merged build finished.
---
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/637#issuecomment-46105643
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15800/
---
If your project is set up for it, you can
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/637#discussion_r12290293
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -912,13 +899,13 @@ class DAGScheduler(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42236810
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/637#issuecomment-42236799
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 markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/637#discussion_r12299198
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -300,13 +300,7 @@ class SparkContext(config: SparkConf) extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42239169
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/637#issuecomment-42239179
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/637#issuecomment-42241323
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14679/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42241319
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42244288
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42244289
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14681/
---
If your project
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/637
SPARK-1715: Ensure actor is self-contained in DAGScheduler
https://issues.apache.org/jira/browse/SPARK-1715
Though the current supervisor-child structure works fine for
fault-tolerance,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42151993
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/637#issuecomment-42151989
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/637#issuecomment-42152912
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14651/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-42152911
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
58 matches
Mail list logo
