Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-148084696
Ping... thoughts on this?
---
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42010427
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,243 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148073949
[Test build #43719 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43719/console)
for PR 9116 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42009023
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,243 @@
+/*
+ * Licensed to the Apache Software
GitHub user jbonofre opened a pull request:
https://github.com/apache/spark/pull/9117
SPARK-2533 - Add locality levels (with tasks count) on job stages summary
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbonofre/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148072768
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/9101#issuecomment-148072767
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/9101#issuecomment-148074489
[Test build #43721 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43721/consoleFull)
for PR 9101 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148088535
[Test build #43722 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43722/consoleFull)
for PR 8954 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9076#issuecomment-148064378
[Test build #1898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1898/console)
for PR 9076 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148074350
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8954#discussion_r42003729
--- Diff:
extras/kinesis-asl/src/test/java/org/apache/spark/streaming/kinesis/JavaKinesisStreamSuite.java
---
@@ -33,9 +35,26 @@
public void
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148087307
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148087283
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/9101#issuecomment-148065089
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148075091
@brkyvz could you fix the test? Otherwise LGTM
---
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42009885
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,243 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148101964
[Test build #43722 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43722/console)
for PR 8954 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148102114
Merged build finished. Test PASSed.
---
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9116#discussion_r42001035
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -694,31 +694,39 @@ class StreamingContext private[streaming] (
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9116#discussion_r42010758
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -694,31 +694,39 @@ class StreamingContext private[streaming] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8954#issuecomment-148102116
Test PASSed.
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/9116#issuecomment-148074154
Merged build finished. Test PASSed.
---
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/9101#issuecomment-148074325
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/9116#issuecomment-148074156
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42004744
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistStrategy.scala ---
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42004674
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistStrategy.scala ---
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148076615
LGTM
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148097686
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148063965
Updated
---
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42008413
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistStrategy.scala ---
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software
Github user a-roberts commented on the pull request:
https://github.com/apache/spark/pull/8995#issuecomment-148102036
Cheers Josh, makes sense, I'm going to test this on our systems before
updating the PR with the changes, here's what I've added (the last parts of
each code block).
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148065120
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148067666
[Test build #43720 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43720/consoleFull)
for PR 9101 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148072707
[Test build #43720 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43720/console)
for PR 9101 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148073612
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
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42004518
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistStrategy.scala ---
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42009817
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,243 @@
+/*
+ * Licensed to the Apache Software
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/8954#discussion_r42009757
--- Diff:
extras/kinesis-asl/src/test/java/org/apache/spark/streaming/kinesis/JavaKinesisStreamSuite.java
---
@@ -33,9 +35,26 @@
public void
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9036#issuecomment-148102351
@marmbrus
Hi Michael, the tests have passed. Please let me know if anything is
pending before it gets merged.
Thanks a lot.
---
If your project is set up
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148116353
Can you post a screenshot for the change?
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9086#discussion_r42020733
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/Decimal.scala ---
@@ -309,10 +319,24 @@ final class Decimal extends Ordered[Decimal] with
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148125649
Sure, give me 2 minutes ;)
---
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/8757#issuecomment-148145424
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148145399
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9038#discussion_r42032759
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregationIterator.scala
---
@@ -481,10 +610,10 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148152254
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9042#issuecomment-148126255
[Test build #1899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1899/consoleFull)
for PR 9042 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148126436
![screen1](https://cloud.githubusercontent.com/assets/158903/10492011/de5d87ac-72a9-11e5-9a00-d70037337a60.png)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148139530
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/8757#issuecomment-148139413
[Test build #43726 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43726/console)
for PR 8757 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148139536
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148144514
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 this
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9098#issuecomment-148147241
Thanks for the 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 does not have this
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9114#discussion_r42020079
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -164,11 +166,16 @@ private void testCmdBuilder(boolean
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9112#issuecomment-148118184
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9112#issuecomment-148118125
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/9106#issuecomment-148122056
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-148129024
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-148128919
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148133941
[Test build #43726 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43726/consoleFull)
for PR 8757 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148145666
[Test build #43727 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43727/consoleFull)
for PR 8757 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148151619
[Test build #43728 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43728/consoleFull)
for PR 9106 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9107#issuecomment-148119645
@navis Thanks for sending out the patch, could you update existing tests to
cover this case (or add a new one)?
---
If your project is set up for it, you can reply to
Github user huaxingao commented on the pull request:
https://github.com/apache/spark/pull/9042#issuecomment-148122772
I looked the error log, it failed at fetching changes from the remote Git
repository. Does it mean something is wrong with my pull request and I need to
do a new
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9101
---
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 alewando commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148127948
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 this
Github user alewando commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148127906
2nd time on this PR for test failure due to (seemingly) network issues
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148141041
It works fine on my machine, however maybe someone else should still test
it. (You can just replace `isSnapshot` with `true` in case you don't want to
change the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9098#issuecomment-148147705
[Test build #1900 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1900/consoleFull)
for PR 9098 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9086#discussion_r42020484
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala
---
@@ -153,13 +153,29 @@ case class Atan(child:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9112#issuecomment-148121320
[Test build #43723 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43723/consoleFull)
for PR 9112 at commit
Github user alewando commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148121104
Fixed
---
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 jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148126672
Note the "new" Locality Levels column in the stage summary view. The format
is:
locality_level(number_of_tasks)
For instance NODE_LOCAL(1), means one
Github user jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/9111#discussion_r42028440
--- Diff: dev/run-tests.py ---
@@ -176,8 +176,9 @@ def determine_java_version(java_exe):
# find raw version string, eg 'java version "1.8.0_25"'
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9098#discussion_r42033329
--- Diff: python/pyspark/mllib/tests.py ---
@@ -252,6 +252,16 @@ def test_sparse_vector_indexing(self):
for ind in [7.8, '1']:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148153768
[Test build #43729 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43729/consoleFull)
for PR 9012 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42017603
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -268,6 +268,12 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148121913
Test PASSed.
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/9101#issuecomment-148121910
Merged build finished. Test PASSed.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148122018
Merging this. Thanks, Tom.
---
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/9106#issuecomment-148122028
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/9106#issuecomment-148126006
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/9106#issuecomment-148126010
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/8453#issuecomment-148130783
[Test build #43725 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43725/consoleFull)
for PR 8453 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148131064
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/8757#issuecomment-148131106
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9101#issuecomment-148121606
[Test build #43721 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43721/console)
for PR 9101 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9053
---
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/9106#issuecomment-148147093
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9098#discussion_r4204
--- Diff: python/pyspark/mllib/tests.py ---
@@ -252,6 +252,16 @@ def test_sparse_vector_indexing(self):
for ind in [7.8, '1']:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148147159
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148146922
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 this
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9098#discussion_r42033324
--- Diff: python/pyspark/mllib/linalg/__init__.py ---
@@ -769,10 +769,10 @@ def __getitem__(self, index):
if index >= self.size or index < 0:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148152323
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-147952967
[Test build #43704 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43704/consoleFull)
for PR 4887 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-147957070
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/4887#issuecomment-147957067
[Test build #43705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43705/console)
for PR 4887 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-147957069
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 does
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-147957284
@andrewor14
For we have three methods to release unroll memory for three situation
1. Unroll success. We expect to cache this block in `tryToPut`. We do not
1 - 100 of 662 matches
Mail list logo