Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53840445
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19452/consoleFull)
for PR 2176 at commit
Github user colorant commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-53841329
Jenkins, test 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 the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-53841355
Jenkins, 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-53841508
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19454/consoleFull)
for PR 1241 at commit
Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53842283
Thanks @rxin . Updated the patch accordingly.
---
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/2176#issuecomment-53842303
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19455/consoleFull)
for PR 2176 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2176#discussion_r16883839
--- Diff: core/src/main/scala/org/apache/spark/FutureAction.scala ---
@@ -149,6 +149,13 @@ class SimpleFutureAction[T] private[spark](jobWaiter:
JobWaiter[_],
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2168#issuecomment-53842447
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19450/consoleFull)
for PR 2168 at commit
Github user lirui-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2176#discussion_r16883922
--- Diff: core/src/main/scala/org/apache/spark/FutureAction.scala ---
@@ -149,6 +149,13 @@ class SimpleFutureAction[T] private[spark](jobWaiter:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53842962
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19452/consoleFull)
for PR 2176 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53843111
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19456/consoleFull)
for PR 2176 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/882#issuecomment-53843747
Jenkins, this is 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-53843808
Jenkins, this is 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2185#issuecomment-53843928
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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1761#issuecomment-53843965
Hi @XuTingjun
Do you mind closing this PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53843990
Jenkins, this is 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-53844028
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-53844406
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19461/consoleFull)
for PR 1977 at commit
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/2193
[SPARK-3296][mllib] spark-example should be run-example in head notation of
DenseKMeans and SparseNaiveBayes
./bin/spark-example should be ./bin/run-example in DenseKMeans and
SparseNaiveBayes
You
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53844439
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19460/consoleFull)
for PR 2191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2193#issuecomment-53844598
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/1241#issuecomment-53844784
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19454/consoleFull)
for PR 1241 at commit
GitHub user ChengXiangLi opened a pull request:
https://github.com/apache/spark/pull/2194
SPARK-2895: Add mapPartitionsWithContext related support on Spark Java API.
You can merge this pull request into a Git repository by running:
$ git pull
18515 exec.cpp:131] Version: 0.19.1
I0829 16:21:04.366479 18546 exec.cpp:205] Executor registered on slave
20140829-160303-3374320138-60030-3252-41
14/08/29 16:21:04 INFO MesosExecutorBackend: Registered with Mesos as
executor ID 20140829-160303-3374320138-60030-3252-41
14/08/29 16:21
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/1964#issuecomment-53845417
@mengxr, @dlwh, @erikerlandson, @rnowling,
Thank you for your feedback.
I agree with that idea which distance metrics/measures are implemented in
Breeze.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2194#issuecomment-53845634
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/2176#issuecomment-53845876
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19455/consoleFull)
for PR 2176 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53846021
You will need to add mima excludes.
---
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 velvia commented on the pull request:
https://github.com/apache/spark/pull/2077#issuecomment-53846528
@rxin what characteristic of each stage allows you to group relevant stages
together into jobs? For example the job server itself can run multiple
jobs on a single
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2077#issuecomment-53846679
Couple different alternatives:
1. Just provide a job to stage mapping for now, since that's a huge step up
from what we have right now which is stage only.
Github user velvia commented on the pull request:
https://github.com/apache/spark/pull/2077#issuecomment-53846867
Ah yes, the job group.
On Fri, Aug 29, 2014 at 12:47 AM, Reynold Xin notificati...@github.com
wrote:
Couple different alternatives:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53846910
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19456/consoleFull)
for PR 2176 at commit
Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53847106
Hi @rxin , could you be more specific as how to do it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53847200
Take a look at the failure message here:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19456/consoleFull
And look at file in project/Mima*
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-53848815
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19461/consoleFull)
for PR 1977 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2171#issuecomment-53849620
test 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
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2171#issuecomment-53849613
Build failure was caused by PySpark, again...
---
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/2171#issuecomment-53850093
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19462/consoleFull)
for PR 2171 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53850264
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19460/consoleFull)
for PR 2191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2188#issuecomment-53851776
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19463/consoleFull)
for PR 2188 at commit
Github user chouqin commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53852376
Sorry, I should to change the file name
`case sensitivity: Hive table-0-5d14d21a239daa42b086cc895215009a` to
`case sensitivity when query Hive
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53853042
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19464/consoleFull)
for PR 2191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2084#issuecomment-53853018
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19465/consoleFull)
for PR 2084 at commit
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-53853095
Hm... Do you know why getCurrentUser is changed after JNI is called? before
jni method calls, getCurrentUser is my id, but after that ID change
---
If your
Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53853736
Thanks @rxin . I updated 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 viirya opened a pull request:
https://github.com/apache/spark/pull/2195
[SPARK-3300][SQL] Should clean old buffer after copying its content
The function `ensureFreeSpace` in object `ColumnBuilder` clears old buffer
before copying its content to new buffer. This PR fixes
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53853915
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19466/consoleFull)
for PR 2176 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53854049
I just noticed that `clear()` would not actually erase the data in the
buffer. So you can close this PR if you think it is not necessary to make the
change.
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53854112
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/1983#issuecomment-53855239
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19467/consoleFull)
for PR 1983 at commit
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/2081#issuecomment-53856243
Wow, you're right, I hadn't read this line before.
When you launch an M3 instance, we ignore any instance store volumes
specified in the block device mapping
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2197
[SPARK-3302] The wrong version information in SparkContext
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3302
Alternatively
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2081#issuecomment-53856587
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19470/consoleFull)
for PR 2081 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53856550
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19469/consoleFull)
for PR 2196 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2197#issuecomment-53856969
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19471/consoleFull)
for PR 2197 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2171#issuecomment-53857182
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19462/consoleFull)
for PR 2171 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2188#issuecomment-53858144
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19463/consoleFull)
for PR 2188 at commit
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-53858688
Do you take an advice about relations ( or issues ) between
UserGroupInformation and JNI? Mesos is a framework written by C++.
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53858994
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19466/consoleFull)
for PR 2176 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2191#issuecomment-53860345
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19464/consoleFull)
for PR 2191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2081#issuecomment-53860410
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19468/consoleFull)
for PR 2081 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2084#issuecomment-53860429
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19465/consoleFull)
for PR 2084 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53861142
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19469/consoleFull)
for PR 2196 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2081#issuecomment-53861228
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19470/consoleFull)
for PR 2081 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2197#issuecomment-53861526
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19471/consoleFull)
for PR 2197 at commit
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1306#issuecomment-53863401
Ok ,Got it, I will close this PR ;
---
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 YanjieGao closed the pull request at:
https://github.com/apache/spark/pull/1306
---
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/1983#issuecomment-53864655
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19467/consoleFull)**
after a configured wait of `120m`.
---
If your project is
Github user rnowling commented on the pull request:
https://github.com/apache/spark/pull/2168#issuecomment-53867935
It seems 3 tests failed but they were unrelated to my changes. The
GraphGeneratorsSuite I added passed without issue.
Are other PRs having similar issues?
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16897472
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16897553
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16897786
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16897811
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16898137
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2169#discussion_r16898249
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -17,18 +17,430 @@
package
Github user sarutak closed the pull request at:
https://github.com/apache/spark/pull/2016
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/2017#issuecomment-53880948
Closing this PR because #2020 resolved this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user sarutak closed the pull request at:
https://github.com/apache/spark/pull/2017
---
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/2138#issuecomment-53880931
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19472/consoleFull)
for PR 2138 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2001#issuecomment-53881604
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19475/consoleFull)
for PR 2001 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-53881683
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19473/consoleFull)
for PR 2078 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-53882879
which JNI call is it changing after? Where are you printing the log
statement from the Executor?
---
If your project is set up for it, you can reply to this email
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53883407
can you separate these 2 changes. The test change would need to go into
master and branch-1.1. The other is just for branch-1.1
---
If your project is set up for it,
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53883744
sure, but SPARK-3177 can't run without pom.xml changes.
On Fri, Aug 29, 2014 at 7:32 AM, Tom Graves notificati...@github.com
wrote:
can
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53884226
Thanks @witgo!
For others: This PR is related to [this comment on another
PR](https://github.com/apache/spark/pull/2175#issuecomment-53795465).
---
If your
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53884482
Just to clear, so you mean I need to
1) close the current PR
2) open two PRs, one for pom.xml changes and another one for test changes ?
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53884847
Yes please close this one. Open just one new one with SPARK-3177 against
master branch and I'll pull back into branch-1.1 also. Leave the pom.xml
change out since
Github user scwf closed the pull request at:
https://github.com/apache/spark/pull/2052
---
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 witgo closed the pull request at:
https://github.com/apache/spark/pull/2197
---
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 chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53887249
sure, will do
On Fri, Aug 29, 2014 at 7:43 AM, Tom Graves notificati...@github.com
wrote:
Yes please close this one. Open just one new
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2138#issuecomment-53888633
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19472/consoleFull)
for PR 2138 at commit
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2198
[SPARK-3304] ApplicationMaster's Finish status is wrong when uncaught
exception is thrown from ReporterThread
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/2199
[SPARK-3303][core] fix SparkContextSchedulerCreationSuite test error
run test with the master branch with this command when mesos native lib is
set
sbt/sbt -Pyarn -Phadoop-2.3
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2199#issuecomment-53889648
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/2175#issuecomment-53889720
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19476/consoleFull)
for PR 2175 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2198#issuecomment-53889989
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19477/consoleFull)
for PR 2198 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2001#issuecomment-53889964
Is this still needed after https://github.com/apache/spark/pull/1180? It
added a call to sc.stop in the YarnClientSchedulerBackend when the application
is
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2185#issuecomment-53890041
Jenkins, test 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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2185#issuecomment-53890029
hmm, odd is jenkins not working.
---
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/2001#issuecomment-53889418
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19475/consoleFull)
for PR 2001 at commit
1 - 100 of 328 matches
Mail list logo
