Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r62281151
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1125,6 +1126,66 @@ setMethod("summarize",
agg(x, ...)
})
+#' dapply
+#'
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r62281013
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1125,6 +1126,66 @@ setMethod("summarize",
agg(x, ...)
})
+#' dapply
+#'
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12493
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215908392
Merging this to master
---
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/12493#issuecomment-215644198
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/12493#issuecomment-215644197
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/12493#issuecomment-215644086
**[Test build #57312 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57312/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215628799
**[Test build #57312 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57312/consoleFull)**
for PR 12493 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215628604
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215619600
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/12493#issuecomment-215619599
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/12493#issuecomment-215619544
**[Test build #57296 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57296/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215611550
**[Test build #57296 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57296/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61526656
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1981,6 +1982,23 @@ class Dataset[T] private[sql](
}
/**
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61522881
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1125,6 +1126,66 @@ setMethod("summarize",
agg(x, ...)
})
+#' dapply
+#'
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215600099
@davies, yes, those changes are deliberately for future PRs, like
applyCollect()
---
If your project is set up for it, you can reply to this email and have your
reply
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61522642
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1981,6 +1982,23 @@ class Dataset[T] private[sql](
}
/**
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215536504
LGTM over all. There are still a few of the change that are not needed by
this PR (for example, SERIALIZED_R_DATA_SCHEMA), are these kept for future?
---
If your
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61487677
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -158,10 +158,15 @@ object EliminateSerialization
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61486972
--- Diff: R/pkg/inst/worker/worker.R ---
@@ -84,6 +84,15 @@ broadcastElap <- elapsedSecs()
# as number of partitions to create.
numPartitions <-
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61486517
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1125,6 +1126,66 @@ setMethod("summarize",
agg(x, ...)
})
+#' dapply
+#'
Github user NarineK commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r61377331
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1981,6 +1982,23 @@ class Dataset[T] private[sql](
}
/**
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215303408
**[Test build #57201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57201/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215303502
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/12493#issuecomment-215303503
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/12493#issuecomment-215287520
Cool R code LGTM. @davies / @rxin If one of you can take a final pass at
the SQL changes this should be good to do.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215286212
**[Test build #57201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57201/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215285083
@shivaram, changed the code. let's wait for the testing result:)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215284725
Yes, I tried, "stringsAsFactors" must be FALSE, as our SerDe does not
support factor for now
so I am changing the code as your proposal
---
If your project is set
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215283979
FWIW I tried the 4 lines I wrote above and it works on my machine. The code
in worker.R looks something like
```
...
+if (isDataFrame) {
+ if
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215281615
Yeah adding a comment to revisit in future sounds good.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215281354
and add a comment for future revisit
---
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215281271
I am not sure if it is necessary to add "stringsAsFactors" as FALSE. just
add for safety. Remove it for now?
---
If your project is set up for it, you can reply to
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215280314
I think the best workaround is to do something like
```
oldOpt <- getOption("stringsAsFactors")
options(stringsAsFactors=FALSE)
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215279975
Aha - I think the option didn't exist before. From
https://cran.r-project.org/src/base/NEWS
```
CHANGES IN R 3.2.4:
The data.frame method of
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215279387
I am using R 3.2.4. I just re-ran the test again with success. OK let me
try some old versions
---
If your project is set up for it, you can reply to this email and
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215278557
Yeah the version on Jenkins is `R version 3.1.1 (2014-07-10)` and on my
laptop is `R version 3.2.1 (2015-06-18)`. I can see the error on my laptop as
well
---
If
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215277993
@shivaram, is the R version on Jenkins 3.1.1? seems I need to test with it
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215208501
@sun-rui I poked around this a little bit more today. It looks like what is
happening is that somehow we are creating `factor` type objects when we have
strings in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215049539
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/12493#issuecomment-215049531
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/12493#issuecomment-215049395
**[Test build #57110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57110/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215017351
**[Test build #57110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57110/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215016426
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215010957
**[Test build #57096 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57096/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-215011127
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/12493#issuecomment-215011131
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/12493#issuecomment-214985926
**[Test build #57096 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57096/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214985318
@shivaram , rebased to master. SparkR unit tests passed on my machine.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214970063
@sun-rui Do the tests pass locally for you ? Because the error in Jenkins
doesn't seem like a flaky test but from the `dapply` test (error pasted below).
Also
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214960152
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214960153
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/12493#issuecomment-214960044
**[Test build #57066 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57066/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214936020
**[Test build #57066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57066/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214935436
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214658265
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/12493#issuecomment-214658264
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/12493#issuecomment-214658254
**[Test build #56983 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56983/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214656686
**[Test build #56983 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56983/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214585898
@shivaram, it may be related to the workaround for SPARK-14803, let me
check it
---
If your project is set up for it, you can reply to this email and have your
reply
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214553151
@sun-rui It looks like some Catalyst tests are failing repeatedly. Can you
check if its related to this PR or not ?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214542583
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/12493#issuecomment-214542589
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/12493#issuecomment-214542146
**[Test build #56918 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56918/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214508934
**[Test build #56918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56918/consoleFull)**
for PR 12493 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507799
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507057
**[Test build #56909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56909/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507478
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/12493#issuecomment-214507476
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 shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214473135
i guess it just likes me more than you both. ;)
i'll triple-check the whitelist and see if something broke there. as
usual, there's nothing in the logs
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214472422
**[Test build #56909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56909/consoleFull)**
for PR 12493 at commit
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214470976
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 shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214470548
it's because the github pull request builder generally sucks. :)
anyways, looking in to it now.
---
If your project is set up for it, you can reply to
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214460886
@shaneknapp Could you check why this PR isn't being picked up by Jenkins ?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214411685
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214269773
Jenkins, retest it 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/12493#issuecomment-214241525
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/12493#issuecomment-214241528
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/12493#issuecomment-214241002
**[Test build #56889 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56889/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214201014
@shivaram, rebased to master
---
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/12493#issuecomment-214200933
**[Test build #56889 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56889/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214139743
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214139748
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/12493#issuecomment-214139137
**[Test build #56871 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56871/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214100961
**[Test build #56871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56871/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r60858977
--- Diff: R/pkg/inst/worker/worker.R ---
@@ -100,7 +109,24 @@ if (isEmpty != 0) {
# Timing reading input data for execution
inputElap <-
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214097354
@NarineK, seems not necessary. but that does not hurt? cc @cloud-fan
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214041344
@sun-rui , It seems that there are some recent changes in logical plans.
Specifically, there is no ObjectOperator in ../logical/object.scala but
ObjectsConsumers and
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213540482
@sun-rui Could you bring this up to date with master ? I think Jenkins is
not running as its not merging cleanly
---
If your project is set up for it, you can reply
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213542906
Pending tests passing, this is overall looking fine to me. @davies / @rxin
will be good if you do one more pass to see if the SQL integration is fine.
---
If your
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/12493#discussion_r60782517
--- Diff: R/pkg/inst/worker/worker.R ---
@@ -100,7 +109,24 @@ if (isEmpty != 0) {
# Timing reading input data for execution
inputElap <-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213380195
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/12493#issuecomment-213380192
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213379654
**[Test build #56686 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56686/consoleFull)**
for PR 12493 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213331807
Jenkins, retest it 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/12493#issuecomment-213331130
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213331135
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/12493#issuecomment-213330411
**[Test build #56663 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56663/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213324258
**[Test build #56686 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56686/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-213315553
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 177 matches
Mail list logo
