Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10030#issuecomment-160431389
**[Test build #46850 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46850/consoleFull)**
for PR 10030 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10024#issuecomment-160438090
**[Test build #46852 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46852/consoleFull)**
for PR 10024 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10024#issuecomment-160438161
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/10024#issuecomment-160438158
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9769
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9543#issuecomment-160474252
@xguo27 Can I ask what is your specific use case for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/10030#discussion_r46098539
--- Diff: R/pkg/inst/tests/testthat/test_mllib.R ---
@@ -26,7 +26,7 @@ sc <- sparkR.init()
sqlContext <- sparkRSQL.init(sc)
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r46098502
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1015,21 +1016,27 @@ class SparkILoop(
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9819#issuecomment-160477160
@hvanhovell Thank you for the PR! Just a quick heads up. We will allocate
time to review during next week (and the week after if we need more time to
work on it).
---
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/9819#issuecomment-160478413
Yes. You can use any Spark aggregate function as a window function. Most
Hive UDAFs should also work except for the pivoted ones...
---
If your project is set up
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160478206
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160478184
**[Test build #46857 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46857/consoleFull)**
for PR 10033 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160478218
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46857/consoleFull
is execurted by worker 3. Let me find another worker.
---
If your project is set
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9819#issuecomment-160478139
One quick question. With this PR, is it possible to use any Spark SQL's
aggregate function as a window function?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10031#issuecomment-160430972
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10032#issuecomment-160450354
**[Test build #46855 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46855/consoleFull)**
for PR 10032 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10032#issuecomment-160450392
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/10032#issuecomment-160450394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mdagost commented on the pull request:
https://github.com/apache/spark/pull/8359#issuecomment-160468431
Nope! Go ahead!
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/10015#issuecomment-160475692
LGTM. Merging to master and 1.6.
---
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 the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160478928
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46858/consoleFull
is in worker 6.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160478873
**[Test build #46858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46858/consoleFull)**
for PR 10033 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9543#discussion_r46098451
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/client/VersionsSuite.scala ---
@@ -45,6 +45,8 @@ class VersionsSuite extends SparkFunSuite with
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160476054
Yep, this [looks pretty
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9553#discussion_r46098497
--- Diff: repl/scala-2.11/src/main/scala/org/apache/spark/repl/Main.scala
---
@@ -78,16 +79,21 @@ object Main extends Logging {
}
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/10033
[SPARK-12039] [TESTS] [test-hadoop1.0] Add maven and apache repos to remote
repos when we want to download jars for metadata hive.
https://issues.apache.org/jira/browse/SPARK-12039
You can merge
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160476237
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160476232
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 CodingCat opened a pull request:
https://github.com/apache/spark/pull/10032
[SPARK-12037][CORE] initialize heartbeatReceiverRef before calling
startDriverHeartbeat
https://issues.apache.org/jira/browse/SPARK-12037
a simple fix by changing the order of the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10032#issuecomment-160431636
**[Test build #46855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46855/consoleFull)**
for PR 10032 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160474727
@zjffdu I feel it is not a good idea to change lots of code just to get a
better error message. Is it possible to have a small change to achieve the goal?
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160476233
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/10030#issuecomment-160431430
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10030#issuecomment-160431431
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9769#issuecomment-160452624
LGTM. Merging 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 have this
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9940#issuecomment-160473565
Is it a regression?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10015
---
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 felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/10030#discussion_r46098765
--- Diff: R/pkg/inst/tests/testthat/test_sparkSQL.R ---
@@ -832,10 +846,10 @@ test_that("test HiveContext", {
expect_equal(count(df2), 3)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160417691
**[Test build #46849 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46849/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160417840
**[Test build #46849 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46849/consoleFull)**
for PR 10029 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160417843
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/10029#issuecomment-160417842
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/10029#issuecomment-160418449
**[Test build #46851 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46851/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9769#issuecomment-160418454
**[Test build #46847 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46847/consoleFull)**
for PR 9769 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9769#issuecomment-160418494
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/9769#issuecomment-160418496
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/10024#issuecomment-160419872
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10024#issuecomment-160420970
**[Test build #46852 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46852/consoleFull)**
for PR 10024 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160421565
**[Test build #46851 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46851/consoleFull)**
for PR 10029 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160421583
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/10029#issuecomment-160421584
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160421665
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-160390673
@rxin I have updated this. Is it ready to merge?
---
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 aa8y opened a pull request:
https://github.com/apache/spark/pull/10028
[SPARK-11962] Add optional getAs functions to Row
getAsOpt[T] functions have been added to Row and GeneicRowWithSchema to get
the values present in a row object optionally. Corresponding tests have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10028#issuecomment-160392284
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/9940#issuecomment-160417281
**[Test build #46848 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46848/consoleFull)**
for PR 9940 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10030#issuecomment-160417530
**[Test build #46850 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46850/consoleFull)**
for PR 10030 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9769#issuecomment-160417514
**[Test build #46847 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46847/consoleFull)**
for PR 9769 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/10029
Add covar_pop and covar_samp.
JIRA: https://issues.apache.org/jira/browse/SPARK-9297
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/10030
[SPARK-12034][SPARKR] Eliminate warnings in SparkR test cases.
This PR:
1. Suppress all known warnings.
2. Cleanup test cases and fix some errors in test cases.
3. Fix errors in
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/10030#issuecomment-160413031
This PR depends on SPARK-11781, will rebase it after the PR for SPARK-11781
get merged into master.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-160422208
**[Test build #46853 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46853/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9940#issuecomment-160422270
**[Test build #46848 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46848/consoleFull)**
for PR 9940 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9940#issuecomment-160422309
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/9940#issuecomment-160422310
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/10031
[SPARK-12009][Yarn]Avoid to re-allocating yarn container while driver want
to stop all Executors
when it is yarn-cluster mode and user had called sc.stop(), but main
function continue to
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9992#discussion_r46093966
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -163,6 +163,8 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10031#issuecomment-160428198
**[Test build #46854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46854/consoleFull)**
for PR 10031 at commit
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/9992#issuecomment-160430008
I have created new PR #10031 to fix this problem. Can you take a look at
it? Thanks.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10031#issuecomment-160430928
**[Test build #46854 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46854/consoleFull)**
for PR 10031 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10031#issuecomment-160430973
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/10034
[SPARK-12019][SPARKR] Check param and fix doc for sparkR.init()
and add tests.
Spark submit expects comma-separated list
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160485305
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/10033#issuecomment-160485294
**[Test build #46858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46858/consoleFull)**
for PR 10033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10033#issuecomment-160485304
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/10034#issuecomment-160486682
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/10034#issuecomment-160486648
**[Test build #46860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46860/consoleFull)**
for PR 10034 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10034#issuecomment-160486681
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/8760#issuecomment-160490927
**[Test build #46861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46861/consoleFull)**
for PR 8760 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-160505192
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/8760#issuecomment-160505191
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 sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/10030#discussion_r46106851
--- Diff: R/pkg/inst/tests/testthat/test_mllib.R ---
@@ -26,7 +26,7 @@ sc <- sparkR.init()
sqlContext <- sparkRSQL.init(sc)
test_that("glm
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8880#issuecomment-160512345
**[Test build #46864 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46864/consoleFull)**
for PR 8880 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8880#issuecomment-160512402
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/8880#issuecomment-160512401
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9982#issuecomment-160513571
By the way, it looks like the test failure which motivated this patch
occurs more frequently than I originally thought. It seems to happen about once
a day, give or
Github user dilipbiswal closed the pull request at:
https://github.com/apache/spark/pull/9981
---
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
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9981#issuecomment-160509630
@cloud-fan Sure.. I will close this PR for now. If you think of a better
approach and need my help in anyway pl let me know. Thanks for your feedback.
---
If your
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/10034#issuecomment-160515406
Hmm I think its better to just support both forms ? Isn't `c("jar1",
"jar2")` more natural ?
---
If your project is set up for it, you can reply to this email and
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9981#issuecomment-160486254
ping @cloud-fan @yhuai
---
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/10034#issuecomment-160487807
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/10034#issuecomment-160487808
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/10034#issuecomment-160487774
**[Test build #46860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46860/consoleFull)**
for PR 10034 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9991#issuecomment-160493581
**[Test build #46862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46862/consoleFull)**
for PR 9991 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160493625
@yhuai Only changing JSONRelation/TextRelation can be a short-term
solution. But since this is a general issue for HadoopFsRelation. so it would
be better to do it in
Github user carsonwang commented on the pull request:
https://github.com/apache/spark/pull/9991#issuecomment-160494777
@vanzin , I wrapped the calls to the hooks with
`Utils.tryLogNonFatalError`. I didn't clean up the `SQLListener` after a
application end event because another
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9804#issuecomment-160495223
**[Test build #46863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46863/consoleFull)**
for PR 9804 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9804#issuecomment-160495869
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/9804#issuecomment-160495866
**[Test build #46863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46863/consoleFull)**
for PR 9804 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9804#issuecomment-160495870
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 169 matches
Mail list logo
