Github user devldevelopment commented on the pull request:
https://github.com/apache/spark/pull/5528#issuecomment-94152524
Looks good and much safer. However, is it still possible to kill a spark
stage externally(outside of the UI or context) via POST even if
spark.ui.killEnabled =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94152858
[Test build #30517 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30517/consoleFull)
for PR 5571 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94152864
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/5572
[SPARK-6307][Core] Speed up RDD.cartesian by caching remotely received
blocks
JIRA: https://issues.apache.org/jira/browse/SPARK-6307 and
https://issues.apache.org/jira/browse/SPARK-6922
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5573#issuecomment-94173522
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94173344
No, just assert that == is true. Looks like the framework actually rejects
use of this method? It didn't say it didn't equal, weirdly
---
If your project is set up for
Github user devldevelopment commented on the pull request:
https://github.com/apache/spark/pull/5528#issuecomment-94152603
Looks much safer. Although is it still possible to kill a stage from an
external client (non-ui) when spark.ui.killEnabled=false?
Similarly what is the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94172856
[Test build #30519 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30519/consoleFull)
for PR 5571 at commit
GitHub user vidma opened a pull request:
https://github.com/apache/spark/pull/5573
Add named field support for sql.Row
It looked weird that up to now there was no way in Spark's Scala API to
access fields of `DataFrame/sql.Row` by name, only by their index.
This tries to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94174451
[Test build #30518 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30518/consoleFull)
for PR 5572 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5528#issuecomment-94174719
Yeah I think that's right, you could still kill a stage by sending a
request directly. That's easy to change. Killing a non-existent stage would
result in some error /
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94175608
@tbertelsen You can't consume an `Iterator` more than once, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user tbertelsen commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94175140
Thanks for taking a crack at this. It helps a lot, but I see a few problems
:)
1. It requires that the user to know of and remembers to set the
configuration
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94168361
[Test build #30518 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30518/consoleFull)
for PR 5572 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94170894
Run the following codes to test the performance:
def randomString() = {
def randChar = 'A' + (math.random * 4).toInt
val length = 1000
Github user ogirardot commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94171708
Seems like the precision for float is needed in the test.
I'll add it back
---
If your project is set up for it, you can reply to this email and have your
reply
Github user ogirardot commented on a diff in the pull request:
https://github.com/apache/spark/pull/5571#discussion_r28644734
--- Diff: core/src/test/java/org/apache/spark/JavaAPISuite.java ---
@@ -762,6 +762,20 @@ public void min() {
}
@Test
+ public void
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94178500
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/5574#issuecomment-94178499
[Test build #30520 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30520/consoleFull)
for PR 5574 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94180488
[Test build #30519 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30519/consoleFull)
for PR 5571 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94180506
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/5571#issuecomment-94180559
[Test build #30521 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30521/consoleFull)
for PR 5571 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94182694
[Test build #30522 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30522/consoleFull)
for PR 5572 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/5572#discussion_r28645610
--- Diff: core/src/main/scala/org/apache/spark/CacheManager.scala ---
@@ -49,7 +49,15 @@ private[spark] class CacheManager(blockManager:
BlockManager) extends
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/5572#discussion_r28645841
--- Diff: core/src/test/scala/org/apache/spark/CacheManagerSuite.scala ---
@@ -82,6 +84,33 @@ class CacheManagerSuite extends FunSuite with
LocalSparkContext
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94186362
[Test build #30524 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30524/consoleFull)
for PR 5572 at commit
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/5575
[SPARK-6955] Perform port retries at NettyBlockTransferService level
Currently we're doing port retries in the TransportServer level, but this
is not specified by the TransportContext API and it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94188022
[Test build #30527 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30527/consoleFull)
for PR 5575 at commit
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94188006
err, cc @andrewor14, not @andrewor13.
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94187977
cc @SaintBacchus @andrewor13 @vanzin This patch aims to resolve SPARK-6955
while keeping the fix for SPARK-5444.
---
If your project is set up for it, you can reply to
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94191773
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94191767
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 feature
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94191765
That sure looks cleaner. Although updating the HTTP client version has some
implications across the code base -- we need to see if we harmonize correctly
on this version
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28646715
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1037,21 +1037,52 @@ private[spark] object Utils extends Logging {
}
Github user tbertelsen commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94176211
@srowen Good point. I was a little too quick there. Then I would add
`toArray` and keep the values locally â unless the cache is really fast,
e.g., not doing
Github user tbertelsen commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94184152
@viirya LGTM, Thanks for your help on this :D
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/5572#discussion_r28645716
--- Diff: core/src/test/scala/org/apache/spark/CacheManagerSuite.scala ---
@@ -82,6 +84,33 @@ class CacheManagerSuite extends FunSuite with
LocalSparkContext
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94184430
[Test build #30523 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30523/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94184407
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/5572#issuecomment-94184401
[Test build #30522 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30522/consoleFull)
for PR 5572 at commit
Github user tbertelsen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5572#discussion_r28645804
--- Diff: core/src/test/scala/org/apache/spark/CacheManagerSuite.scala ---
@@ -82,6 +84,33 @@ class CacheManagerSuite extends FunSuite with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5570#issuecomment-94186349
[Test build #30525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30525/consoleFull)
for PR 5570 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94187636
[Test build #30526 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30526/consoleFull)
for PR 5575 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94187639
[Test build #30526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30526/consoleFull)
for PR 5575 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94187640
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/5537#issuecomment-94187864
Ah, I realize now that the original change that brought this bug up (#4240)
was perhaps not the right solution. The issue that #4240 solved was actually
brought up
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28646439
--- Diff:
network/common/src/main/java/org/apache/spark/network/util/ByteUnit.java ---
@@ -0,0 +1,165 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94191887
[Test build #30528 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30528/consoleFull)
for PR 5354 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94191866
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user calvinjia commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94178568
@JoshRosen @srowen @aarondav
I've updated the PR to resolve the http client issue by upgrading the
version and specifying the version in sql/hive (which was
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94179447
@tbertelsen Good point. I agree with the idea 1. I will update it later.
I was thinking to add a parameter as you did to `RDD.iterator`. I use the
configuration
Github user tbertelsen commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94181452
@viirya I understand your api concern. For compatibility we could give the
parameter to `iterator` a default value. FWIW The documentation of `iterator()`
states that
Github user tbertelsen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5572#discussion_r28645695
--- Diff: core/src/test/scala/org/apache/spark/CacheManagerSuite.scala ---
@@ -82,6 +84,33 @@ class CacheManagerSuite extends FunSuite with
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5510#issuecomment-94190375
@petro-rudenko what do you think about this instead? returning 1 empty map
does make some sense viewed from this perspective. Does it cause a problem you
can't work
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94190468
LGTM. Though I imagine this is not controversial, I would love to get a nod
from @JoshRosen or @pwendell or @rxin as it offers a new API method.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5570#issuecomment-94190959
[Test build #30525 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30525/consoleFull)
for PR 5570 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5570#issuecomment-94190966
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28646660
--- Diff:
network/common/src/main/java/org/apache/spark/network/util/ByteUnit.java ---
@@ -0,0 +1,165 @@
+/*
+ * Licensed to the Apache Software
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28646672
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1037,21 +1037,52 @@ private[spark] object Utils extends Logging {
}
GitHub user ilganeli opened a pull request:
https://github.com/apache/spark/pull/5574
[SPARK-5932][CORE][WIP] Use consistent naming for size properties
I've added an interface to JavaUtils to do byte conversion. I will add
hooks within Utils.scala to handle conversion within Spark
Github user ilganeli commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94178418
Also will need to update ```memoryStringToMb``` to use the new interface.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ogirardot commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94180136
I pushed the modifications,
The third time is always the winning one ! :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94190443
[Test build #30521 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30521/consoleFull)
for PR 5571 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94190445
Test PASSed.
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/5574#discussion_r28646409
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1037,21 +1037,52 @@ private[spark] object Utils extends Logging {
}
Github user ogirardot commented on the pull request:
https://github.com/apache/spark/pull/5571#issuecomment-94190848
of course, have a nice weekend :)
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94191861
[Test build #30523 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30523/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-94193910
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/5572#issuecomment-94193906
[Test build #30524 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30524/consoleFull)
for PR 5572 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94196568
[Test build #30529 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30529/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94198381
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/5574#discussion_r28646866
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1037,21 +1037,52 @@ private[spark] object Utils extends Logging {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94200251
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/5574#issuecomment-94200323
[Test build #30534 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30534/consoleFull)
for PR 5574 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94200250
[Test build #30533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30533/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-9429
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user ilganeli commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94200154
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94200103
[Test build #30533 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30533/consoleFull)
for PR 5574 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-9425
[Test build #30532 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30532/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94203515
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/5354#issuecomment-94203512
[Test build #30528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30528/consoleFull)
for PR 5354 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94203562
[Test build #30529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30529/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94203565
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28646823
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1037,21 +1037,52 @@ private[spark] object Utils extends Logging {
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94199111
**[Test build #30527 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30527/consoleFull)**
for PR 5575 at commit
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/5467#issuecomment-94197937
@jkbradley Thinking over it again, I'm not sure if it would offer a great
advantage to do so. If you are talking about preventing this slicing
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94198324
[Test build #30530 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30530/consoleFull)
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5575#issuecomment-94199113
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/5574#discussion_r28647113
--- Diff:
core/src/main/scala/org/apache/spark/serializer/KryoSerializer.scala ---
@@ -49,9 +49,9 @@ class KryoSerializer(conf: SparkConf)
with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5144#issuecomment-94199115
[Test build #30531 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30531/consoleFull)
for PR 5144 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94198380
[Test build #30530 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30530/consoleFull)
for PR 5574 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5144#issuecomment-94202176
[Test build #30531 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30531/consoleFull)
for PR 5144 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5144#issuecomment-94202182
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5561#issuecomment-94214123
LGTM, so I'm going to merge this to master. Thanks Nick!
---
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/5525#issuecomment-94215300
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5525#issuecomment-94215352
[Test build #30538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30538/consoleFull)
for PR 5525 at commit
GitHub user gaurav324 opened a pull request:
https://github.com/apache/spark/pull/5576
Fixed doc
Just fixed a doc.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gaurav324/spark master
Alternatively you can review and apply
Github user ilganeli commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-94215412
I actually wouldn't mind working on this - it's an issue near and dear to
my heart :-). What's the best way to pick up the ball here ? I could just make
a new PR - the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5288#issuecomment-94215466
[Test build #30540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30540/consoleFull)
for PR 5288 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5288#issuecomment-94215494
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 181 matches
Mail list logo
