Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2803#issuecomment-59317667
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/2803#issuecomment-59317650
Jenkins, test this please. @liancheng - I am getting a SQL failure here
that seems like it might be legitimate but I'm having trouble interpreting why
it could possibly
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59317882
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/2812#issuecomment-59317878
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21791/consoleFull)
for PR 2812 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2803#issuecomment-59317948
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21794/consoleFull)
for PR 2803 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2799#issuecomment-59318015
Thanks Prashant - I merged 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2799
---
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59318221
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2087#discussion_r18939560
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -121,6 +125,31 @@ class SparkHadoopUtil extends Logging {
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2726#issuecomment-59318575
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2087#discussion_r18939658
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -121,6 +125,31 @@ class SparkHadoopUtil extends Logging {
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2087#discussion_r18939679
--- Diff: core/src/main/scala/org/apache/spark/rdd/HadoopRDD.scala ---
@@ -222,12 +221,33 @@ class HadoopRDD[K, V](
case eof: EOFException =
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2087#issuecomment-59318880
Yeah you are totally right - the performance bit was not correct from my
end. I added some more comments on this.
---
If your project is set up for it, you can reply
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2087#discussion_r18939723
--- Diff:
core/src/test/scala/org/apache/spark/metrics/InputMetricsSuite.scala ---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2819#issuecomment-59319145
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21790/consoleFull)
for PR 2819 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2819#issuecomment-59319148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2743#discussion_r18939808
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -65,9 +66,12 @@ private[spark] class PythonRDD(
val localdir =
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2743#discussion_r18939813
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -53,7 +53,8 @@ private[spark] class PythonRDD(
extends
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2743#discussion_r18939839
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -53,7 +53,8 @@ private[spark] class PythonRDD(
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59319365
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/2812#issuecomment-59319438
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-59319525
What if we just add the maven-shade plug-in but we configure it in a way
where it effectively is doing no operations? I.e. we add a relocation of a
class that does not
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-59319582
I think that a solution that doesn't require us using our own plug-in is
good, even if we do something silly like we have to shade a class that is in
fact un-used.
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/2821
[HOTFIX][SQL] missing golden file for SPARK-3807
create golden file for SPARK-3807
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59319859
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21796/consoleFull)
for PR 2812 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2821#issuecomment-59320188
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21797/consoleFull)
for PR 2821 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2820#issuecomment-59320277
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/2820#issuecomment-59320272
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21792/consoleFull)
for PR 2820 at commit
GitHub user dajac opened a pull request:
https://github.com/apache/spark/pull/2822
SPARK-3965: Ensure that Spark assembly for hadoop2 contains avro-mapred for
hadoop2
When building current Spark assembly for hadoop2, the wrong version of
avro-mapred is picked. This patch adds
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2822#issuecomment-59321034
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/2743#issuecomment-59321587
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21798/consoleFull)
for PR 2743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59321684
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/383/consoleFull)
for PR 2743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2701#issuecomment-59322320
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21793/consoleFull)
for PR 2701 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2701#issuecomment-59322329
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/2821#issuecomment-59322559
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/2821#issuecomment-59322554
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21797/consoleFull)
for PR 2821 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2803#issuecomment-59322774
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21794/consoleFull)
for PR 2803 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2821#issuecomment-59322715
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2803#issuecomment-59322777
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/2821#issuecomment-59323161
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21799/consoleFull)
for PR 2821 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59323505
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21796/consoleFull)
for PR 2812 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2812#issuecomment-59323510
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/2810#issuecomment-59326697
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21800/consoleFull)
for PR 2810 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59327830
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21798/consoleFull)
for PR 2743 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59327837
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/2743#issuecomment-59327910
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/383/consoleFull)
for PR 2743 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2821#issuecomment-59328172
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/2821#issuecomment-59328169
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21799/consoleFull)
for PR 2821 at commit
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/2789#issuecomment-59329218
Added support for Bitwise AND(), OR(|) ,XOR(^), NOT(~) in this PR only.
Please review it.
---
If your project is set up for it, you can reply to this email and have
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-59331286
Even if we do this trick and shade something in all artifacts, what about
spark-parent ? There since we don't build jar shading plugin throws NPEs.
---
If your
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2241#discussion_r18944242
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala ---
@@ -288,23 +290,26 @@ class HiveContext(sc: SparkContext) extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2810#issuecomment-59333977
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21800/consoleFull)
for PR 2810 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2810#issuecomment-59333984
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2800#issuecomment-59335440
This LGTM, 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 have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2800#issuecomment-59335748
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/384/consoleFull)
for PR 2800 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2823
[SQL] Fixes the race condition that may cause test failure
The removed `Future` was used to end the test case as soon as the Spark SQL
CLI process exits. When the process exits prematurely, this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2823#issuecomment-59341971
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21801/consoleFull)
for PR 2823 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59342873
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21802/consoleFull)
for PR 2816 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2823#issuecomment-59345187
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/2823#issuecomment-59345184
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21801/consoleFull)
for PR 2823 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59345860
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/2816#issuecomment-59345856
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21802/consoleFull)
for PR 2816 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59346655
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21803/consoleFull)
for PR 2816 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2800#issuecomment-59347603
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/384/consoleFull)**
for PR 2800 at commit
Github user luogankun commented on the pull request:
https://github.com/apache/spark/pull/2800#issuecomment-59348084
@liancheng Tests timed out!
---
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/771#issuecomment-59350133
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21804/consoleFull)
for PR 771 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59351094
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21803/consoleFull)
for PR 2816 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59351102
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/2800#issuecomment-59354966
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/385/consoleFull)
for PR 2800 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18952642
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18952637
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18952768
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18952827
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18952854
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18953268
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -323,11 +373,11 @@ class SqlParser extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/771#issuecomment-59358046
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18953527
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/771#issuecomment-59358035
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21804/consoleFull)
for PR 771 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18953740
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2816#discussion_r18953909
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -301,17 +301,67 @@ class SqlParser extends
Github user ssjssh commented on the pull request:
https://github.com/apache/spark/pull/2813#issuecomment-59359408
can someone 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 project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2800#issuecomment-59361067
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/385/consoleFull)
for PR 2800 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/2824
[SPARK-3948][Shuffle]Fix stream corruption bug in sort-based shuffle
Kernel 2.6.32 bug will lead to unexpected behavior of transferTo in
copyStream, and this will corrupt the shuffle output file
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/2824#discussion_r18956465
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -280,12 +280,29 @@ private[spark] object Utils extends Logging {
// When
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2814#issuecomment-59365761
I addressed the MIMA warnings, two of which were just caused by the class
being renamed.
I'm less sure about the warning around `PairRDDFunctions` since
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2814#issuecomment-59366632
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21806/consoleFull)
for PR 2814 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/2824#discussion_r18957257
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -280,12 +280,29 @@ private[spark] object Utils extends Logging {
// When
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59367830
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/2824#issuecomment-59368192
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21807/consoleFull)
for PR 2824 at commit
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/2824#discussion_r18957913
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -280,12 +280,29 @@ private[spark] object Utils extends Logging {
// When
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-59369912
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/387/consoleFull)
for PR 2770 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-59375645
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/387/consoleFull)
for PR 2770 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/2825
SPARK-3969 Optimizer should have a super class as an interface.
Some developers want to replace `Optimizer` to fit their projects but can't
do so because currently `Optimizer` is an `object`.
You
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/2826
Remove duplicate removal of local dirs
The shutdown hook of `DiskBlockManager` would remove localDirs. So do not
need to register them with `Utils.registerShutdownDeleteDir`. It causes
duplicate
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2825#issuecomment-59379459
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21808/consoleFull)
for PR 2825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2826#issuecomment-59379911
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/2824#issuecomment-59380188
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21807/consoleFull)
for PR 2824 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59380201
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/2814#issuecomment-59381926
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21806/consoleFull)
for PR 2814 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2814#issuecomment-59381939
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 378 matches
Mail list logo
