Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/5114#discussion_r26910223
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/ReceiverInputDStream.scala
---
@@ -54,6 +55,14 @@ abstract class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-84575878
**[Test build #28958 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28958/consoleFull)**
for PR 4960 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5063#issuecomment-84587905
**[Test build #28959 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28959/consoleFull)**
for PR 5063 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5063#issuecomment-84587909
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/5126#issuecomment-84590493
**[Test build #28960 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28960/consoleFull)**
for PR 5126 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5127#issuecomment-84601340
**[Test build #28961 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28961/consoleFull)**
for PR 5127 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5127#issuecomment-84601341
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5087
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/5087#issuecomment-84548034
Thanks! Merged into master and branch-1.3.
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/4685#discussion_r26900980
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -18,21 +18,28 @@
package
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84593285
Actually, there are about 15 other instances of `-class.html` URLs that
appear to not work. I'm going to make a JIRA to fix them all:
Github user kamilsmuga commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84596359
Is documentation generated somehow or you guys just using static markdown
files?
Found 19 matches across 6 files in docs. Fixing it.
---
If your project is set
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84599277
[Test build #28963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28963/consoleFull)
for PR 3890 at commit
Github user nyaapa commented on a diff in the pull request:
https://github.com/apache/spark/pull/5115#discussion_r26902472
--- Diff:
core/src/main/scala/org/apache/spark/deploy/LocalSparkCluster.scala ---
@@ -53,7 +53,7 @@ class LocalSparkCluster(
/* Start the Master */
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84599278
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84614077
@srowen Yes, All tests passed in the test log. Do you know what the problem
is?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84574953
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5115#discussion_r26902267
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -792,6 +793,11 @@ private[spark] object Utils extends Logging {
lazy val
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84599908
API docs are generated but the source that needs fixing here is in the
markdown.
For example in http://spark.apache.org/docs/latest/mllib-data-types.html
there
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84609099
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/3890#issuecomment-84609071
[Test build #28964 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28964/consoleFull)
for PR 3890 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/5129
[SPARK-6452] [SQL] Checks for missing attributes and unresolved operator
for all types of operator
In `CheckAnalysis`, `Filter` and `Aggregate` are checked in separate case
clauses, thus never
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/5125
[SPARK-6428] Added explicit types for all public methods in core.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark core-explicit-type
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4685#issuecomment-84560878
Actually, how about adding type checking in individual SQL functions, while
leaving type conversions in a centralized place? As type conversion rules are
fewer and
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4685#issuecomment-84564133
@kai-zeng I just updated the title and description of SPARK-6444, would you
mind to add SPARK-6444 to your PR title?
---
If your project is set up for it, you can
Github user nyaapa commented on a diff in the pull request:
https://github.com/apache/spark/pull/5115#discussion_r26901850
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -792,6 +793,11 @@ private[spark] object Utils extends Logging {
lazy val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84590507
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5074#issuecomment-84600412
@sryza any more thoughts? I think this is pretty good now.
---
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 kamilsmuga commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84603519
In the middle of refactoring I realised my fork is 440+ commits behind
upstream. I did merge with upstream - that's why 13240cb shows up.
Anyways, can you please
Github user kamilsmuga commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84606794
Now I have. Username: smugakamil
---
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
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4685#issuecomment-84558771
I like the idea of compile time type checking. This could be generalized to
all UDFs. For example, `Like` and `RLike` should also check whether their
arguments are of
Github user kai-zeng commented on the pull request:
https://github.com/apache/spark/pull/4685#issuecomment-84567894
@liancheng Sure, no problem.
---
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 yuhc opened a pull request:
https://github.com/apache/spark/pull/5128
[SPARK-6455] [docs] Correct some mistakes and typos
Correct some typos. Correct a mistake in lib/PageRank.scala. The first
PageRank implementation uses standalone Graph interface, but the second uses
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84605560
That's fine, the commits will be squashed anyway. You generally just push
new commits, and if you need to resolve a merge conflict with `master`, then
use `rebase`.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84608248
[Test build #28964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28964/consoleFull)
for PR 3890 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5128#issuecomment-84612782
LGTM. Just trivial doc fixes and so I don't think they even deserve a
Jenkins test (which is having a bit of trouble at the moment.) I verified that
the example comment
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84546495
[Test build #28957 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28957/consoleFull)
for PR 5125 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5122
---
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/5126#issuecomment-84591337
[Test build #28962 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28962/consoleFull)
for PR 5126 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5115#discussion_r26902255
--- Diff:
core/src/main/scala/org/apache/spark/deploy/LocalSparkCluster.scala ---
@@ -53,7 +53,7 @@ class LocalSparkCluster(
/* Start the Master */
Github user nyaapa commented on a diff in the pull request:
https://github.com/apache/spark/pull/5115#discussion_r26902451
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -792,6 +793,11 @@ private[spark] object Utils extends Logging {
lazy val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5129#issuecomment-84611682
[Test build #28965 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28965/consoleFull)
for PR 5129 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-84548578
[Test build #28958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28958/consoleFull)
for PR 4960 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4685#issuecomment-84557697
I believe this PR fixes [SPARK-6444] [1], whose root cause is `Sum` doesn't
check for data type.
[1]: https://issues.apache.org/jira/browse/SPARK-6444
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84574940
**[Test build #28957 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28957/consoleFull)**
for PR 5125 at commit
GitHub user jongyoul opened a pull request:
https://github.com/apache/spark/pull/5126
[SPARK-6453][Mesos] Some Mesos*Suite have a different package with their
classes
- Moved Suites from o.a.s.s.mesos to o.a.s.s.cluster.mesos
You can merge this pull request into a Git repository
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-84575882
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/5127#issuecomment-84586830
[Test build #28961 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28961/consoleFull)
for PR 5127 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84591254
LGTM. That does look like a small oversight.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84591238
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 have
Github user kamilsmuga commented on the pull request:
https://github.com/apache/spark/pull/5120#issuecomment-84598835
Just took a look DOM elements and looks like permalinks are properly
generated. E.g.
```a class=headerlink href=#pyspark.mllib.stat.Statistics.colStats
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84598782
[Test build #28963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28963/consoleFull)
for PR 3890 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5128#issuecomment-84606388
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5118#issuecomment-84565167
[Test build #28956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28956/consoleFull)
for PR 5118 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5118#issuecomment-84565237
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/5063#issuecomment-84564916
[Test build #28959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28959/consoleFull)
for PR 5063 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/5127
[SPARK-6444] [SQL] A quick fix for SPARK-6444
As explained in the JIRA ticket [comment] [1], this PR introduces a simple
quick fix for SPARK-6444. The root cause of this issue is that we don't
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84611003
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/5126#issuecomment-84610999
**[Test build #28962 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28962/consoleFull)**
for PR 5126 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84612289
The test looks like some strange unrelated failure in building the final
assembly. All tests actually pass, so I think this PR (which just moves tests,
which pass) is OK.
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3895#issuecomment-84628348
Haven't got time to investigate why so many (hundreds) tests failed. Will
come back to this one later.
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5128
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5126
---
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/5129#issuecomment-84643066
**[Test build #28965 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28965/consoleFull)**
for PR 5129 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3222#issuecomment-84656209
So, this hasn't been touched in a couple months, and doesn't merge. It
overlaps with some existing functionality in MLlib, and some other works in
progress. It's really a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3822#issuecomment-84656511
[Test build #28966 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28966/consoleFull)
for PR 3822 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3822#issuecomment-84639226
[Test build #28966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28966/consoleFull)
for PR 3822 at commit
Github user debasish83 commented on the pull request:
https://github.com/apache/spark/pull/3890#issuecomment-84624771
Can we discuss it in JIRA ? For svm with owlqn what's the orthant wise
constraint you are adding ? There are ways to handle the max differentiability
in bfgs as well
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4688#issuecomment-84641612
[Test build #28967 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28967/consoleFull)
for PR 4688 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5120
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3822#issuecomment-84656534
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4909#issuecomment-84656423
If this particular PR isn't going to be updated, mind closing this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/4854#issuecomment-84663088
@catmonkeylee I created a JIRA here:
[https://issues.apache.org/jira/browse/SPARK-6457] If you can, please comment
on the JIRA; I'll add suggestions there. Thanks!
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4688#issuecomment-84666327
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/4688#issuecomment-84666314
[Test build #28967 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28967/consoleFull)
for PR 4688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5129#issuecomment-84643069
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/3822#issuecomment-84639059
rebased
---
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 debasish83 commented on the pull request:
https://github.com/apache/spark/pull/3221#issuecomment-84643641
I am adding ml.QuadraticSolver tests that builds upon normal equation
(similar to CholeskySolver tests) for 1 - 5 basically...will update in a bit...
---
If your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5112#issuecomment-84657493
LGTM - @jkbradley I suppose we can merge this and ... keep SPARK-6337 open
or is it worth just making a new JIRA should any other doc issues come up? (or
just a follow-on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5128#issuecomment-84680484
I fixed the build here :
https://github.com/apache/spark/commit/7a0da47708b0e6b117b5c1a35aa3e93b8a914d5f
---
If your project is set up for it, you can reply to this email
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5128#issuecomment-84679719
Sean this broke the build!
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84677924
[Test build #28968 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28968/consoleFull)
for PR 5125 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84696159
[Test build #28969 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28969/consoleFull)
for PR 5125 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84696185
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5129#discussion_r26906084
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -199,4 +199,21 @@ class AnalysisSuite extends FunSuite
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84681097
[Test build #28969 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28969/consoleFull)
for PR 5125 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5129#discussion_r26906097
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -85,14 +85,19 @@ class CheckAnalysis {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84676626
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 have
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5129#discussion_r26906086
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -85,14 +85,19 @@ class CheckAnalysis {
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5128#issuecomment-84681443
Ah! of course the line length now fails the style check; it didn't
line-break. Well that'll teach me to eye-ball even a trivial doc change. Very
sorry about that and
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5112#issuecomment-84685217
Resolving the JIRA sounds fine to me.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5112
---
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 debasish83 commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-84708094
@witgo there are lot of useful building blocks in your RBM PR...are you
planning to consolidate them in this PR ?
---
If your project is set up for it, you can reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4867
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/4867#issuecomment-84668071
Merged into master, thanks!
---
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/5125#issuecomment-84677028
[Test build #28968 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28968/consoleFull)
for PR 5125 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84677937
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5125#issuecomment-84680821
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5126#issuecomment-84575680
[Test build #28960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28960/consoleFull)
for PR 5126 at commit
GitHub user ryan-williams opened a pull request:
https://github.com/apache/spark/pull/5130
Report failure status if driver throws exception
e.g. OutOfMemoryError on the driver was leading to application
reporting SUCCESS on history server and to YARN RM.
You can merge this pull
1 - 100 of 181 matches
Mail list logo
